mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] bootm: Add option to force booting signed images
Date: Fri, 22 Jan 2016 08:35:40 +0100	[thread overview]
Message-ID: <20160122073540.GP13058@pengutronix.de> (raw)
In-Reply-To: <CAGm1_kvriwy-P1VHiq91cEmJHOpWR3VHu9q4SQWGU+PjRkJoTQ@mail.gmail.com>

Hi Yegor,

On Tue, Jan 19, 2016 at 09:03:17AM +0100, Yegor Yefremov wrote:
> Hi Sascha,
> 
> On Tue, Jan 19, 2016 at 8:55 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > With CONFIG_BOOTM_FORCE_SIGNED_IMAGES the bootm code will refuse to boot
> > unsigned images. Since currently FIT is the only image type which
> > supports signing this means we with this option we enforce using FIT
> 
> comma is missing after "supports signing", "we" after "means" must go away
> 
> > images. All additionally passed in device trees and initrds will be
> 
> a word is missing between "All" and "additionally"

I think not, I reread the sentence and it still makes sense to me.

I fixed the other things you mentioned.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2016-01-22  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  7:55 Sascha Hauer
2016-01-19  8:03 ` Yegor Yefremov
2016-01-22  7:35   ` Sascha Hauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160122073540.GP13058@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=yegorslists@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox