From: pgsellmann@portner-elektronik.at (Peter Gsellmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: AT91: add board support for Pcontrol_G20
Date: Mon, 18 Oct 2010 10:00:29 +0200 [thread overview]
Message-ID: <1287388829.1450.21.camel@aspire.localdomain> (raw)
In-Reply-To: <AANLkTik8qZdU6o+ArBJkUGFNGaN2Ucmkj3kxKKudtRBE@mail.gmail.com>
Am Freitag, den 15.10.2010, 18:31 +0200 schrieb avictor.za at gmail.com:
> hi,
>
> On Fri, Oct 15, 2010 at 3:50 AM, Jean-Christophe PLAGNIOL-VILLARD
> <plagnioj@jcrosoft.com> wrote:
> > On 16:14 Thu 14 Oct , Russell King - ARM Linux wrote:
> >> On Thu, Oct 14, 2010 at 04:47:47PM +0200, Nicolas Ferre wrote:
> >> > > diff --git a/arch/arm/configs/pcontrol_g20_defconfig b/arch/arm/configs/pcontrol_g20_defconfig
> >> > > new file mode 100644
> >>
> >> Is it really necessary to have another platform specific defconfig rather
> >> than grouping it together with other similar platforms?
> > I'm working on it to merge the cpu and boards together hope to finish it
> > before the end of the merge window
>
> What's the point of having a board supported by the kernel, if you
> don't include a configuration file to actually make the board usable?
>
In this scenario, i (and all other board maintainers) have to test the
merged defconfig on my board after the merge.
If it fails, i have either to maintain a private version of defconfig :-(
or to checkin the needed changes which triggers the same task for (n-1)
board maintainers.
Regards,
Peter
next prev parent reply other threads:[~2010-10-18 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 15:41 [PATCH] ARM: AT91: add board support for Pcontrol_G20 Peter Gsellmann
2010-10-08 12:34 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-08 15:10 ` Peter Gsellmann
2010-10-11 9:02 ` [PATCH v2] " Peter Gsellmann
2010-10-11 10:22 ` [PATCH v3] " Peter Gsellmann
2010-10-13 13:15 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-13 14:18 ` [PATCH v4] " Peter Gsellmann
2010-10-14 14:47 ` Nicolas Ferre
2010-10-14 15:14 ` Russell King - ARM Linux
2010-10-15 1:50 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-15 16:31 ` avictor.za at gmail.com
2010-10-18 8:00 ` Peter Gsellmann [this message]
2010-10-19 9:25 ` Nicolas Ferre
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=1287388829.1450.21.camel@aspire.localdomain \
--to=pgsellmann@portner-elektronik.at \
--cc=linux-arm-kernel@lists.infradead.org \
/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