From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: Updated mach-types update
Date: Wed, 23 Mar 2011 10:31:57 +0100 [thread overview]
Message-ID: <20110323093157.GA6397@vixen> (raw)
In-Reply-To: <20110322193026.GC17264@n2100.arm.linux.org.uk>
Hi,
On Tue, Mar 22, 2011 at 07:30:26PM +0000, ext Russell King - ARM Linux wrote:
> On Tue, Mar 22, 2011 at 02:19:11PM +0100, Domenico Andreoli wrote:
> > On Sun, Mar 20, 2011 at 12:03 PM, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> > >
> > > What this means is that any platform in the machine database which has not
> > > been submitted to mainline for 12 months since it was registered will be
> > > automatically dropped from the file, and the platform maintainer will need
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > to either talk to me to get it reinstated before submission, or update the
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > entry in some way to 'freshen' it.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >
> >
> > I think this statement matches the needs of those, like me, are trying to
> > add a new board.
> > My patch [0] applies but does not build any more. How does it work in this
> > case?
>
> Precisely in the way I said above - see the bit I've underlined.
So it looks like I cannot be of any help improving my QQ2440 patch :)
Could you please reintroduce the qq2440 mach type? I have one patch
[0] sitting, I got some feedback but nobody has Revieved-by the v3 yet.
The networking part has been already pulled by Linus trough netdev.
Thank you.
> > anyway I would add some comment in mach-types that explains how the files is
> > managed.
>
> You mean like the comment that's in there - have you even looked at the
> cut down version yet?
Yes, after I sent the email. It took a while for me to find your git
tree, it was not obvious that rmk is you :) Sorry for the noise.
Regards,
Domenico
[0] http://article.gmane.org/gmane.linux.ports.arm.kernel/110583/match=qq2440
next prev parent reply other threads:[~2011-03-23 9:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 11:03 Updated mach-types update Russell King - ARM Linux
2011-03-20 11:41 ` Russell King - ARM Linux
2011-03-24 17:59 ` Tony Lindgren
2011-05-13 11:54 ` Tony Lindgren
2011-05-13 12:19 ` Jarkko Nikula
2011-05-13 14:40 ` [PATCH] omap: Remove support for omap2evm (Re: Updated mach-types update) Tony Lindgren
2011-05-14 16:30 ` Mark Brown
2011-05-16 13:45 ` Liam Girdwood
2011-05-13 14:53 ` Updated mach-types update Tomi Valkeinen
2011-03-21 22:41 ` Detlef Vollmann
2011-03-21 23:10 ` Russell King - ARM Linux
2011-03-21 23:33 ` Detlef Vollmann
2011-03-22 13:19 ` Domenico Andreoli
2011-03-22 19:30 ` Russell King - ARM Linux
2011-03-23 9:31 ` Domenico Andreoli [this message]
2011-03-23 16:37 ` H Hartley Sweeten
2011-03-26 22:52 ` Colin Cross
2011-03-26 23:14 ` Russell King - ARM Linux
2011-03-28 18:00 ` Russell King - ARM Linux
2011-03-28 18:02 ` Russell King - ARM Linux
2011-05-21 1:35 ` Jaya Kumar
2011-05-22 9:11 ` Russell King - ARM Linux
2011-05-23 14:52 ` Arnd Bergmann
2011-05-23 14:59 ` Russell King - ARM Linux
2011-05-23 15:10 ` Mark Brown
2011-05-23 15:33 ` Russell King - ARM Linux
2011-05-23 16:39 ` Arnd Bergmann
2011-05-24 11:00 ` Jaya Kumar
2011-05-24 11:51 ` Arnd Bergmann
2011-07-27 12:20 ` Mark Brown
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=20110323093157.GA6397@vixen \
--to=cavokz@gmail.com \
--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