All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: Default machine include placements
Date: Mon, 25 Jan 2010 21:48:29 +0000	[thread overview]
Message-ID: <20100125214828.GX26562@trinity.fluff.org> (raw)
In-Reply-To: <20100125145935.GB22481@n2100.arm.linux.org.uk>

On Mon, Jan 25, 2010 at 02:59:35PM +0000, Russell King - ARM Linux wrote:
> On Mon, Jan 25, 2010 at 01:54:45PM +0000, Ben Dooks wrote:
> > On Mon, Jan 25, 2010 at 12:04:54PM +0000, Russell King - ARM Linux wrote:
> > > Given the above, and the "mass population" hasn't happened, maybe part
> > > of the solution to the duplicated header file problem is to start
> > > combining some of these directories?
> > 
> > For plat-s3c64xx/mach-s3c6400/mach-s3c6410 how about moving the
> > plat-s3c64xx in with the machine definitions, as it is quite clear
> > now that it is unlikely to have any friends to join it (dev work is
> > on s5p and onwards).
> > 
> > Either arch/arm/mach-s3c64xx and have all s3c6400 and s3c6410 machines
> > in there, or keep the two mach- directories... I think i'd prefer to
> > see the two directories culled into one.
> 
> I'd prefer that too.

Ok, thanks.
 
> > For the s3c24xx case, it probably is the best case to merges s3c2440 and
> > s3c2442 into mach-s3c244x as they are pretty similar.
> > 
> > s3c2443 is on list of things to expand, it is a different beast to the
> > predecessors.
> 
> Sounds like a reason to keep it separate for the time being.
> 
> > I'll try making patches for this tomorrow and see what people think?
> 
> I'm not sure where mach-s3c24a0 fits in to this stuff - the only thing
> it seems to contain is a load of include files.
> 
> With these changes, it's going to take it from 10 mach-s[35]* directories
> down to 8.  Not sure if it makes much material difference to mach/*.h
> includes though.

Should be an improvement, we've already got V210 and C110 into the
same dir (really just packaging options) and I'll look at culling
the C100 and plat-c11x as this line looks like it ended with the
C100 and the newer devices are differrent beasts.
 
-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2010-01-25 21:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25  4:02 Default machine include placements Ben Dooks
2010-01-25  4:02 ` Ben Dooks
2010-01-25 10:05 ` Russell King - ARM Linux
2010-01-25 10:05   ` Russell King - ARM Linux
2010-01-25 10:28   ` Ben Dooks
2010-01-25 10:28     ` Ben Dooks
2010-01-25 10:32   ` Daniel Silverstone
2010-01-25 10:44     ` Ben Dooks
2010-01-25 10:49       ` Daniel Silverstone
2010-01-25 10:55         ` Ben Dooks
2010-01-25 11:19           ` Russell King - ARM Linux
2010-01-25 11:53             ` Ben Dooks
2010-01-25 12:04               ` Russell King - ARM Linux
2010-01-25 13:54                 ` Ben Dooks
2010-01-25 14:59                   ` Russell King - ARM Linux
2010-01-25 21:48                     ` Ben Dooks [this message]
2010-01-25 14:03                 ` Ben Dooks
2010-01-25 10:57       ` Mark Brown
2010-01-25 10:49 ` Ben Dooks
2010-01-25 10:49   ` Ben Dooks
2010-01-25 11:01   ` Russell King - ARM Linux
2010-01-25 11:01     ` Russell King - ARM Linux
2010-01-25 11:44     ` Ben Dooks
2010-01-25 11:44       ` Ben Dooks

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=20100125214828.GX26562@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --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.