Message-ID: <1373908589.2062.18.camel@joe-AO722>
Subject: Re: [PATCH-v3 00/17] staging/lustre: fix various build issues
From: Joe Perches <joe@perches.com>
To: Peng Tao <bergwolf@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org, Fengguang Wu <fengguang.wu@intel.com>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Andreas Dilger <andreas.dilger@intel.com>
Date: Mon, 15 Jul 2013 10:16:29 -0700
In-Reply-To: <1373898440-14208-1-git-send-email-bergwolf@gmail.com>
References: <1373898440-14208-1-git-send-email-bergwolf@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 781
Lines: 19

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/