From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] Create package/freescale-imx directory With current version and download site
Date: Thu, 9 May 2013 23:55:41 +0200 [thread overview]
Message-ID: <20130509235541.6a916afe@skate> (raw)
In-Reply-To: <1368121316-3645-2-git-send-email-h.fijnvandraat@inter.nl.net>
Dear Henk Fijnvandraat,
The first line of your commit log is too long. A commit log should look
like:
"""
A first line of less than ~80 characters to summarize the commit
Some more paragraphs here to explain what you're doing. The important
thing is that there is an empty new line between the summary line, and
the following paragraphs.
And some more details.
Signed-off-by: Someone <foo@bar.com>
"""
On Thu, 9 May 2013 19:41:53 +0200, Henk Fijnvandraat wrote:
> diff --git a/package/freescale-imx/Config.in b/package/freescale-imx/Config.in
> new file mode 100644
> index 0000000..8d0e347
> --- /dev/null
> +++ b/package/freescale-imx/Config.in
> @@ -0,0 +1,16 @@
> +comment "freescale-imx is only relevant for the i.MXxx series from Freescale"
> + depends on BR2_arm
> +
> +menuconfig BR2_PACKAGE_IMX
> + bool "freescale-imx"
> + depends on BR2_arm
> + help
> + This option enables the selection of some packages specific for
> + the i.MXxx series of processors from Freescale.
> + freescale-imx needs an imx-specific kernel to be built
> +
> +
> +if BR2_PACKAGE_IMX
> +source "package/freescale-imx/imx-lib/Config.in"
> +source "package/freescale-imx/firmware-imx/Config.in"
> +endif
This doesn't work: you're moving the packages only in PATCH 2/4.
We try to make patches bisectable: i.e, the code should work at any
point in the patch series. Imagine what happens if your PATCH 1/4 gets
applied and not the following ones.
Suggestion:
* PATCH 1 adds freescale-imx/Config.in and freescale-imx/freescale.mk,
but the Config.in doesn't source the imx-lib/Config and
firmware-imx/Config.in.
* PATCH 2 moves the imx-lib package into package/freescale-imx/
* PATCH 3 moves the firmware-imx package into package/freescale-imx/
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-09 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 17:41 [Buildroot] firmware-imx and imx-lib refactoring Henk Fijnvandraat
2013-05-09 17:41 ` [Buildroot] [PATCH 1/4] Create package/freescale-imx directory With current version and download site Henk Fijnvandraat
2013-05-09 21:55 ` Thomas Petazzoni [this message]
2013-05-09 17:41 ` [Buildroot] [PATCH 2/4] Move firmware-imx and imx-lib to freescale-imx and refactor them Henk Fijnvandraat
2013-05-09 21:56 ` Thomas Petazzoni
2013-05-09 17:41 ` [Buildroot] [PATCH 3/4] Reflect changes in package/Config.in Remove original firmware-imx and imx-lib packages Henk Fijnvandraat
2013-05-09 17:41 ` [Buildroot] [PATCH 4/4] Restyle firmware-imx.mk header Henk Fijnvandraat
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=20130509235541.6a916afe@skate \
--to=thomas.petazzoni@free-electrons.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