From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Simek <monstr@monstr.eu>,
Chen Liqin <liqin.chen@sunplusct.com>
Subject: Re: [PATCH 00/16] asm-generic headers, v4
Date: Thu, 14 May 2009 09:28:01 +0200 [thread overview]
Message-ID: <200905140928.01861.arnd@arndb.de> (raw)
In-Reply-To: <20090514164521.c2b61893.sfr@canb.auug.org.au>
On Thursday 14 May 2009, Stephen Rothwell wrote:
> Hi Arnd,
>
> On Wed, 13 May 2009 22:56:23 +0000 Arnd Bergmann <arnd@arndb.de> wrote:
> >
> > Stephen, can you add
> > git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic next
> > to linux-next?
>
> I will try this tomorrow. It will be interesting to see just how many
> conflicts we get.
Thanks!
I've tried to make this patch set as non-invasive as possible, basically
just adding files and making single line changes to existing files
where necessary. I've never seen conflicts when I tried merging
with linux-next/master.
In the beginning, I was thinking about doing one series per file,
adding the asm-generic version in one patch and changing the per-arch
versions to use it in follow-on patches.
Hopefully, the way I'm doing it now turns out to be less time consuming,
as I can add all the generic headers once without impacting any of the
architectures, and the next patches can easily be done in the
arch maintainer tree for all files at once.
Arnd <><
next prev parent reply other threads:[~2009-05-14 7:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 22:56 [PATCH 00/16] asm-generic headers, v4 Arnd Bergmann
2009-05-13 22:56 ` [PATCH 01/15] asm-generic: rename termios.h, signal.h and mman.h Arnd Bergmann
2009-05-14 5:11 ` Stephen Rothwell
2009-05-14 6:16 ` Sam Ravnborg
2009-05-14 6:43 ` Stephen Rothwell
2009-05-13 22:56 ` [PATCH 02/15] asm-generic: introduce asm/bitsperlong.h Arnd Bergmann
2009-05-13 22:56 ` [PATCH 03/15] asm-generic: add generic sysv ipc headers Arnd Bergmann
2009-05-13 22:56 ` [PATCH 04/15] asm-generic: add generic ABI headers Arnd Bergmann
2009-05-13 22:56 ` [PATCH 05/15] asm-generic: add a generic unistd.h Arnd Bergmann
2009-05-13 22:56 ` [PATCH 06/15] asm-generic: rename atomic.h to atomic-long.h Arnd Bergmann
2009-05-13 22:56 ` [PATCH 07/15] asm-generic: rename page.h and uaccess.h Arnd Bergmann
2009-05-13 22:56 ` [PATCH 08/15] asm-generic: make pci.h usable directly Arnd Bergmann
2009-05-13 22:56 ` [PATCH 09/15] asm-generic: make bitops.h usable Arnd Bergmann
2009-05-13 22:56 ` [PATCH 10/15] asm-generic: add generic versions of common headers Arnd Bergmann
2009-05-13 22:56 ` [PATCH 11/15] asm-generic: add legacy I/O header files Arnd Bergmann
2009-05-13 22:56 ` [PATCH 12/15] asm-generic: add generic atomic.h and io.h Arnd Bergmann
2009-05-13 22:56 ` [PATCH 13/15] asm-generic: add generic NOMMU versions of some headers Arnd Bergmann
2009-05-13 22:56 ` [PATCH 14/15] asm-generic: add a generic uaccess.h Arnd Bergmann
2009-05-13 22:56 ` [PATCH 15/15] add generic lib/checksum.c Arnd Bergmann
2009-05-14 6:45 ` [PATCH 00/16] asm-generic headers, v4 Stephen Rothwell
2009-05-14 7:28 ` Arnd Bergmann [this message]
2009-05-14 7:28 ` Arnd Bergmann
2009-05-14 7:48 ` Stephen Rothwell
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=200905140928.01861.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
--cc=monstr@monstr.eu \
--cc=sfr@canb.auug.org.au \
/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