lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200905140928.01861.arnd@arndb.de>
Date:	Thu, 14 May 2009 09:28:01 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	Michal Simek <monstr@...str.eu>,
	Chen Liqin <liqin.chen@...plusct.com>
Subject: Re: [PATCH 00/16] asm-generic headers, v4

On Thursday 14 May 2009, Stephen Rothwell wrote:
> Hi Arnd,
> 
> On Wed, 13 May 2009 22:56:23 +0000 Arnd Bergmann <arnd@...db.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 <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ