linux-kernel - Re: [PATCH-v3 00/17] staging/lustre: fix various build issues

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Jul 2013 10:16:29 -0700
From:	Joe Perches <joe@...ches.com>
To:	Peng Tao <bergwolf@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org,
	Fengguang Wu <fengguang.wu@...el.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andreas Dilger <andreas.dilger@...el.com>
Subject: Re: [PATCH-v3 00/17] staging/lustre: fix various build issues

On Mon, 2013-07-15 at 22:27 +0800, Peng Tao wrote:
> Hi Greg,
> 
> Now that 3.11-rc1 is out, please consider queuing following patches to
> fix various Lustre client build issues. I've verified that we can now
> pass build on sparc/mips/s390/powerpc/x86, both 32bits and 64bits.

These patches apply to linus' current, but not to -next
where other lustre patches have already been applied.

What's the goal here?  Are you going to ask for the
patches in -next to be reverted or are you going to
respin these patches for -next instead?

--
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/