[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140730161517.GA22229@lst.de>
Date: Wed, 30 Jul 2014 18:15:17 +0200
From: Christoph Hellwig <hch@....de>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Christoph Hellwig <hch@....de>,
Josh Boyer <jwboyer@...oraproject.org>,
Vladimir Davydov <vdavydov@...allels.com>,
linux-scsi@...r.kernel.org,
Mailing-List fedora-kernel <kernel@...ts.fedoraproject.org>,
poma <pomidorabelisima@...il.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Christoph Lameter <cl@...ux.com>
Subject: Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69
kmem_cache_create+0x1a9/0x330()
On Wed, Jul 30, 2014 at 07:04:59PM +0400, James Bottomley wrote:
> It's been remarkably current, I believe ... it's already up to date.
I've updated the drivers tree today and it will get a few more updates
さoon.
> However, we only have 2 -next builds between now and the anticipated
> 3.16 release (unless Linus does another -rc) so there's not enough time
> for a patch that isn't already in (although this one is).
Yes, that's why I'm not eager to complicate things.
> > If James wants to cherry pick it and send it on at this time that might
> > still work fine, but he seems fairly busy.
>
> I'll pull it out and refactor the tree.
I'd rather stop rebasing this close to the release. Linus never had
problems if he got a commit twice due to a cherry pick.
--
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