public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: lauri.hintsala@bluegiga•com (Lauri Hintsala)
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 11:32:20 +0200	[thread overview]
Message-ID: <4EEF04A4.5050804@bluegiga.com> (raw)
In-Reply-To: <20111219091506.GA16097@n2100.arm.linux.org.uk>

On 12/19/2011 11:15 AM, Russell King - ARM Linux wrote:
> On Mon, Dec 19, 2011 at 09:13:22AM +0000, Russell King - ARM Linux wrote:
>> On Mon, Dec 19, 2011 at 05:19:17PM +0800, Shawn Guo wrote:
>>> 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.
>
> Also, whether Veli-Pekka Peltola is should still be the current owner
> or whether there's someone more appropriate to be looking after this
> entry (eg, the active platform maintainer) ?

Correct values:

Type ID:  	3712
Machine name:  	Bluegiga APX4 Development Kit
Machine type:  	apx4devkit
Type macro:  	machine_is_apx4devkit()
Kconfig macro:  	CONFIG_MACH_APX4DEVKIT (this should be fixed)
Type identifier:  	MACH_TYPE_APX4DEVKIT (this should be fixed)

Veli-Pekka is my colleague and it is ok to keep him as contact person. 
Thanks in advance.

BR,
Lauri

  reply	other threads:[~2011-12-19  9:32 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
2011-12-19  9:15         ` Russell King - ARM Linux
2011-12-19  9:32           ` Lauri Hintsala [this message]
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=4EEF04A4.5050804@bluegiga.com \
    --to=lauri.hintsala@bluegiga$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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