Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] board/freescale/common/imx: make imx8-bootloader-prepare more generic
Date: Thu, 19 Jul 2018 10:07:23 +0200	[thread overview]
Message-ID: <20180719100723.4e421707@windsurf> (raw)
In-Reply-To: <20180719080023.GA23715@g751.home>

Hello,

On Thu, 19 Jul 2018 10:00:54 +0200, Gary Bisson wrote:

> > I don't think it's worth keeping some kind of "backward compatibility"
> > here. Just change configs/freescale_imx8mqevk_defconfig to pass the DTB
> > name as argument.  
> 
> Fair enough, I'm fine with that. However, should I keep the check on the
> arguments number to throw an error if no argument is provided?
> 
> Or is the check on UBOOT_DTB existence sufficient?

I think the latter is sufficient.

Or, alternatively, change the script radically to use getopt to avoid
using positional arguments. But I don't think it's worth the effort for
now, just keep things simple.

> I'll wait for a day before respinning the series to see if there are
> other comments.
> 
> Also, not related to the patch, the series doesn't appear "properly" in
> the mailing list archive, patches aren't answers to the cover letter.
> Other strange thing in Patchwork, patch 4/5 is part of "Untitled series
> #56383" instead of the real series, is it normal?
> I just want to make sure I'm not missing some settings in my
> git-send-email config although it just seems that the server
> received/treated the emails in the wrong order.

This is a known patchwork limitation. Your e-mails arrived out of order
(I was initially missing patch 3/5 here and the cover letter, and they
arrived a few minutes later). When e-mails arrive out of order,
patchwork gets confused and is not able to assign patches to the proper
series. IOW, there's no problem on your side, it's patchwork that
doesn't behave properly.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-19  8:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  7:32 [Buildroot] [PATCH 0/5] Add Boundary Devices Nitrogen8M support Gary Bisson
2018-07-19  7:32 ` [Buildroot] [PATCH 1/5] board/freescale/common/imx: make imx8-bootloader-prepare more generic Gary Bisson
2018-07-19  7:45   ` Thomas Petazzoni
2018-07-19  8:00     ` Gary Bisson
2018-07-19  8:07       ` Thomas Petazzoni [this message]
2018-07-19  7:32 ` [Buildroot] [PATCH 2/5] board/boundarydevices: update post-build.sh for i.MX8MQ platforms Gary Bisson
2018-07-19  7:58   ` Thomas Petazzoni
2018-07-19  8:03     ` Gary Bisson
2018-07-19  8:08       ` Thomas Petazzoni
2018-07-19  8:15         ` Gary Bisson
2018-07-19  7:32 ` [Buildroot] [PATCH 3/5] board/boundarydevices: remove obsolete u-boot scripts Gary Bisson
2018-07-19  7:59   ` Thomas Petazzoni
2018-07-19  7:32 ` [Buildroot] [PATCH 4/5] board/boundarydevices: add i.MX8MQ support to " Gary Bisson
2018-07-19  7:32 ` [Buildroot] [PATCH 5/5] configs/nitrogen8m: Add new defconfig Gary Bisson
2018-07-19  8:10   ` Thomas Petazzoni
2018-07-19  8:23     ` Gary Bisson
2018-07-19  8:32       ` Thomas Petazzoni
2018-07-26  8:20       ` Arnout Vandecappelle
2018-07-26  8:51         ` Gary Bisson
2018-07-26  8:54           ` Arnout Vandecappelle

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=20180719100723.4e421707@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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