All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] [ARM] mach-types: Re-add apf9328
Date: Mon, 17 Oct 2011 10:17:49 +0100	[thread overview]
Message-ID: <20111017091749.GF21648@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111017084421.GD21648@n2100.arm.linux.org.uk>

On Mon, Oct 17, 2011 at 09:44:21AM +0100, Russell King - ARM Linux wrote:
> http://www.arm.linux.org.uk/developer/machines/download.php?q=1
> 
> will be the exact file if I were to update it right now (that's the
> URL it's retrieved from.)
> 
> One of the problems we now have is that I no longer have visibility
> of platforms going into mainline (I only find out after they've been
> merged into mainline), so I've no way to update the database with
> that information before I do an update - my information will be up
> to three months out of date.  This in turn means that the 12 month
> grace period can expire and the entries deleted from the merged file
> _after_ they've been merged and queued up elsewhere.
> 
> As I've already said, this has now become one very big unmanagable
> problem.  It needs someone to spend a lot of time at each update
> manually verifying every addition and removal (and kicking those
> people who botch their entries up - which given my interpretation of
> the data protection act means it can only be me).
> 
> I haven't committed an update since August, and at this point in the
> cycle, I'm not going to before this merge window - the risks of breaking
> something already merged or queued up are just too great to consider
> doing so now.
> 
> Longer term, I don't have an answer to this problem - I don't think
> there is a workable answer to a distributed development model with
> a centralized ID database with a grace period on 'unused' entries.

And while we're discussing this issue...

+v7pxa_dt               MACH_V7PXA_DT           V7PXA_DT                3794
+v7mmp_dt               MACH_V7MMP_DT           V7MMP_DT                3795

Why do we have DT-based IDs being registered?  DT does not use machine
IDs in any shape or form.  For DT platforms, machine_is_xxx() must not
be used because it's meaningless.

#define DT_MACHINE_START(_name, _namestr)               \
static const struct machine_desc __mach_desc_##_name    \
 __used                                                 \
 __attribute__((__section__(".arch.info.init"))) = {    \
        .nr             = ~0,                           \
        .name           = _namestr,

Note the .nr = ~0 there.

  reply	other threads:[~2011-10-17  9:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 15:19 [PATCH 1/2] [ARM] mach-types: Re-add apf9328 Gwenhael Goavec-Merou
2011-10-08 15:19 ` [PATCH 2/2] [ARM] MX1:apf9328: Add i2c support Gwenhael Goavec-Merou
2011-10-08 19:27   ` Wolfram Sang
2011-10-11 15:26     ` gwenhael.goavec
2011-10-25  9:36   ` gwenhael.goavec
2011-10-25 11:47     ` Russell King - ARM Linux
2011-10-26  7:40     ` Sascha Hauer
2011-10-08 19:26 ` [PATCH 1/2] [ARM] mach-types: Re-add apf9328 Wolfram Sang
2011-10-08 22:07   ` Russell King - ARM Linux
2011-10-13  9:06     ` Uwe Kleine-König
2011-10-13  9:59       ` Russell King - ARM Linux
2011-10-17  8:44       ` Russell King - ARM Linux
2011-10-17  9:17         ` Russell King - ARM Linux [this message]
2011-10-21 10:10         ` Bedia, Vaibhav
2011-10-21 18:03           ` Russell King - ARM Linux
2011-10-24  8:19             ` Bedia, Vaibhav

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=20111017091749.GF21648@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.