linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: READ THIS: the next mach-types update
Date: Fri, 16 Sep 2011 08:31:59 +0100	[thread overview]
Message-ID: <20110916073159.GC22533@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110915145022.GM28104@game.jcrosoft.org>

On Thu, Sep 15, 2011 at 04:50:22PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 11:25 Thu 15 Sep     , Russell King - ARM Linux wrote:
> > I'm going to be merging a mach-types update (the cut-down and the
> > policy-conforming version) for the next merge window.  This will mean
> > that things WILL BREAK, and I will not notice that things have broken.
> > 
> > In order to fix this, entries need to be fixed to conform to the
> > requirements - where the machine_is_xxx() name is the same as the
> > MACH_TYPE_xxx name and the CONFIG_MACH_xxx name too.
> > 
> > Moreover, entries older than 12 months which have not been merged will
> > be removed.  It is not possible to automatically check for machine_is_xxx()
> > usages as these could conflict with other architectures, and I'm
> > certainly NOT checking for them by hand (I estimate that'd take a
> > significant amount of manual effort to do.)  What that means is that it
> > is _important_ to get the core platform support in _first_ before any
> > drivers which may make use of this.
> > 
> > The following will be deleted from the file this time around are:
> > -ts_x09                  MACH_TS209              TS209                   1565
> > -at572d940hfek           MACH_AT572D940HFEB      AT572D940HFEB           1783
> can be dropped the at572d940hfek as the at572d940hf is drop from mainline
> 
> Russell an you confirm you will re-add the usb-a9g20 and the folowing one
> 
> usb_a9g20               MACH_USB_A9G20          USB_A9G20               1841
> qil_a9g20               MACH_QIL_A9G20          QIL_A9G20               1844
> tny_a9260               MACH_TNY_A9260          TNY_A9260               2058
> tny_a9g20               MACH_TNY_A9G20          TNY_A9G20               2059
> tny_a9263               MACH_TNY_A9263          TNY_A9263               2140

Here's the two relevent question:
1. have they been submitted or edited within the last 12 months?  No.
2. are they merged into mainline?  No.

So will they be in the update?  No.

  reply	other threads:[~2011-09-16  7:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 10:25 READ THIS: the next mach-types update Russell King - ARM Linux
2011-09-15 14:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-16  7:31   ` Russell King - ARM Linux [this message]
2011-09-17  2:51     ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-15 15:26 ` Arnd Bergmann
2011-09-15 19:11   ` Russell King - ARM Linux
2011-09-15 19:32     ` Nicolas Pitre
2011-09-15 18:05 ` Olof Johansson
2011-09-16 10:27 ` Richard Cochran
2011-09-18 15:44   ` Arnd Bergmann
2011-09-19 15:51     ` Richard Cochran
2011-09-17 14:28 ` Pedanekar, Hemant
2011-09-17 14:34   ` Russell King - ARM Linux
2011-09-19 14:51     ` Pedanekar, Hemant
2011-09-19 23:13 ` H Hartley Sweeten
2011-10-17 10:56   ` Russell King - ARM Linux
2011-10-17 11:22     ` Arnd Bergmann
2011-10-17 16:57       ` H Hartley Sweeten

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=20110916073159.GC22533@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).