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

[Greg Kroah-Hartman]

On Tue, Jul 16, 2013 at 10:21:23AM +0800, Peng Tao wrote:
> On Tue, Jul 16, 2013 at 8:07 AM, Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> > On Mon, Jul 15, 2013 at 12:13:57PM -0700, Andrew Morton wrote:
> >> On Mon, 15 Jul 2013 11:40:30 -0700 Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >> > On Mon, Jul 15, 2013 at 10:16:29AM -0700, Joe Perches wrote:
> >> > > 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 trees are those in?  I have nothing in my staging-next branch right
> >> > now, so they didn't come from there, which is where I will be applying
> >> > this to.
> >>
> >> See the five patches I sent you on July 8 ;)
> >>
> >> I'll resend.
> >
> > I got them, I couldn't apply them until after -rc1 is out, so I'll queue
> > them up later this week.
> >
> Hi Greg and Andrew,
> 
> One issue with the five patches is that the shrinker API change is not
> in Linus' tree. So if Greg merges them in staging tree, Lustre cannot
> build there. Is it OK to break in staging tree and just to make sure
> -next can build?

lustre can't build anyway, so what's the issue?  :)

I'll not apply those patches, don't worry, the shrinker stuff needs to
stay in Andrew's tree until it hits Linus's.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/