From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] DEVELOPERS: Fix file order list maintained by me
Date: Wed, 5 Sep 2018 23:46:32 +0200 [thread overview]
Message-ID: <20180905234632.31088798@windsurf> (raw)
In-Reply-To: <1535963172-6664-1-git-send-email-jagan@amarulasolutions.com>
Hello Jagan,
On Mon, 3 Sep 2018 10:26:09 +0200, Jagan Teki wrote:
> -F: configs/amarula_a64_relic_defconfig
The support for this board is not merged yet. If you send patches that
depend on other patches, you should send them all in a patch series.
But in this case, you should have rather based this patch series on
master or next, and not on your branch that contains some unrelated
work such as the Amarula A64 Relic board support.
Anyway, I've fixed this up, and applied to master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-05 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 8:26 [Buildroot] [PATCH 1/4] DEVELOPERS: Fix file order list maintained by me Jagan Teki
2018-09-03 8:26 ` [Buildroot] [PATCH 2/4] board: orangepi: Add Orangepi One Plus support Jagan Teki
2018-09-03 8:26 ` [Buildroot] [PATCH 3/4] configs: bpi-m64: Use Mainline ARM ATF Jagan Teki
2018-09-03 9:06 ` Andre Przywara
2018-09-03 10:37 ` Jagan Teki
2018-09-05 21:48 ` Thomas Petazzoni
2018-09-03 8:26 ` [Buildroot] [PATCH 4/4] configs: bpi-m64: bump linux, uboot Jagan Teki
2018-09-03 14:43 ` Luca Ceresoli
2018-09-04 8:21 ` Thomas Petazzoni
2018-09-05 21:46 ` Thomas Petazzoni [this message]
2018-09-06 15:48 ` [Buildroot] [PATCH 1/4] DEVELOPERS: Fix file order list maintained by me Jagan Teki
2018-09-06 15:51 ` Thomas Petazzoni
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=20180905234632.31088798@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