From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit
Date: Mon, 19 Dec 2011 09:13:22 +0000 [thread overview]
Message-ID: <20111219091322.GD14542@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111219091916.GJ4962@S2100-06.ap.freescale.net>
On Mon, Dec 19, 2011 at 05:19:17PM +0800, Shawn Guo wrote:
> On Mon, Dec 19, 2011 at 09:13:16AM +0200, Lauri Hintsala wrote:
> > On 12/19/2011 09:13 AM, Shawn Guo wrote:
> > >The patch looks good.
> >
> > Thank you for your time.
> >
> >
> > >The only problem I have is I do not see MACH_TYPE_APX4DEVKIT defined
> > >in arch/arm/tools/mach-types on either Linus' tree or linux-next
> > >tree. I'm afraid that we will experience the same problem we have
> > >experienced with m28evk patch, which broke the whole mxs build for a
> > >couple of early -rc of v3.2.
> >
> > I see the problem. What is your suggestion? Should we create patch
> > to add APX4DEVKIT to mach-types file as you did last time?
> > http://permalink.gmane.org/gmane.linux.ports.arm.kernel/140425
> >
> > We have register apx4devkit to ARM machine database. Machine id of
> > apx4devkit is 3712. For some reason "Kconfig macro" and "type
> > identifier" are out of sync in db. DEVKIT string is missing from
> > those.
> > http://www.arm.linux.org.uk/developer/machines/list.php?id=3712
> >
> Hi Russell,
>
> We have seen APX4DEVKIT in the ARM machine database. But you did not
> include it in the commit aef1c03 (ARM: Update mach-types) which is
> sitting on -next. Can you please include it as we plan to merge the
> board support during the coming merge window?
No. It will be automatically removed from any update as long as it does
not conform to the requirements - that is, in this case, the strings
being out of sync indentified in the message to which you replied to.
Someone needs to tell me what the correct entry is supposed to look like.
next prev parent reply other threads:[~2011-12-19 9:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 9:02 [PATCH v3] ARM: mxs: Add initial support for Bluegiga APX4 Development Kit Lauri Hintsala
2011-12-16 6:07 ` Lauri Hintsala
2011-12-16 6:53 ` Shawn Guo
2011-12-19 7:13 ` Shawn Guo
2011-12-19 7:13 ` Lauri Hintsala
2011-12-19 9:19 ` Shawn Guo
2011-12-19 9:13 ` Russell King - ARM Linux [this message]
2011-12-19 9:15 ` Russell King - ARM Linux
2011-12-19 9:32 ` Lauri Hintsala
2011-12-19 9:44 ` Shawn Guo
2011-12-19 11:18 ` Veli-Pekka Peltola
2012-01-04 13:52 ` Shawn Guo
2012-01-04 21:18 ` Russell King - ARM Linux
2012-01-05 11:31 ` Russell King - ARM Linux
2012-01-05 12:15 ` Shawn Guo
2012-01-05 12:08 ` Lauri Hintsala
2012-03-30 13:13 ` Shawn Guo
2012-03-30 13:15 ` Russell King - ARM Linux
2012-03-30 13:20 ` Russell King - ARM Linux
2012-04-26 7:42 ` Lauri Hintsala
2012-04-26 7:48 ` Shawn Guo
2012-04-26 7:55 ` Lauri Hintsala
2012-03-30 13:22 ` Shawn Guo
2012-03-30 13:28 ` Russell King - ARM Linux
2012-03-30 22:43 ` Nicolas Pitre
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=20111219091322.GD14542@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).