public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: monstr@seznam.cz,
	Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
	John Williams <john.williams@petalogix.com>,
	jwboyer@linux.vnet.ibm.com, benh@kernel.crashing.org,
	John Linn <John.Linn@xilinx.com>,
	git-dev@xilinx.com, Grant Likely <grant.likely@secretlab.ca>,
	git@xilinx.com, microblaze-uclinux@itee.uq.edu.au,
	linux-kernel@vger.kernel.org, paulus@samba.org
Subject: Re: Microblaze Linux release
Date: Mon, 14 Apr 2008 08:55:14 +0200	[thread overview]
Message-ID: <200804140855.14892.arnd@arndb.de> (raw)
In-Reply-To: <4802E749.2040809@zytor.com>

On Monday 14 April 2008, H. Peter Anvin wrote:
> Arnd Bergmann wrote:
> > 
> > One of the things I always wanted to have is a common location for all the
> > things that get duplicated verbatim into each new architecture, like all
> > the include/asm/{fcntl,ioctls,ipcbuf,mman,poll,posix_types,sem_buf}.h and
> > others that define part of the syscall ABI.
> > 
> 
> include/asm-generic

Sure. Halfway through writing my sentence, I wanted to suggest arch/generic
for the stuff in there that has the potential of being unified, but then
realized how little there is of that, and that it may just as well go into
the top-level mm/, kernel/, lib/ etc, as we have done in the past.

	Arnd <><

  reply	other threads:[~2008-04-14  6:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 13:26 Microblaze Linux release Michal Simek
2008-04-13 13:33 ` Grant Likely
2008-04-13 15:44   ` Michal Simek
2008-04-13 15:13 ` Josh Boyer
2008-04-13 18:50   ` Michal Simek
2008-04-14 15:55     ` Stephen Neuendorffer
2008-04-15 12:59       ` Michal Simek
2008-04-14  3:38 ` Arnd Bergmann
2008-04-14  5:10   ` H. Peter Anvin
2008-04-14  6:55     ` Arnd Bergmann [this message]
2008-04-14  6:01   ` Arnd Bergmann
2008-04-15 12:54     ` Michal Simek
2008-04-15 13:32       ` Arnd Bergmann
2008-04-15 21:52         ` Benjamin Herrenschmidt
2008-04-16  6:24           ` Michal Simek
2008-04-16  7:31             ` Paul Mackerras
2008-04-16  7:44               ` Arnd Bergmann
2008-04-16 15:28                 ` Michal Simek
2008-04-16 15:33                   ` Arnd Bergmann
2008-04-23 20:55                     ` Michal Simek
2008-04-23 20:57                       ` Florian Fainelli
2008-04-23 21:01                         ` Arnd Bergmann
2008-04-23 21:08                           ` Michal Simek
2008-04-23 21:22                         ` Michal Simek
2008-04-23 22:51                           ` John Williams
2008-04-16 15:26               ` Michal Simek
2008-04-16  7:45             ` Benjamin Herrenschmidt
2008-04-23 21:35           ` Michal Simek
2008-04-23 20:57         ` Michal Simek
2008-04-18 17:56       ` [microblaze-uclinux] " Stephen Neuendorffer
2008-04-19 10:38         ` Michal Simek
2008-04-14  7:10   ` Michal Simek

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=200804140855.14892.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=John.Linn@xilinx.com \
    --cc=benh@kernel.crashing.org \
    --cc=git-dev@xilinx.com \
    --cc=git@xilinx.com \
    --cc=grant.likely@secretlab.ca \
    --cc=hpa@zytor.com \
    --cc=john.williams@petalogix.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=monstr@seznam.cz \
    --cc=paulus@samba.org \
    --cc=stephen.neuendorffer@xilinx.com \
    /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