linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Christoph Hellwig <hch@lst.de>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Vladimir Davydov <vdavydov@parallels.com>,
	linux-scsi@vger.kernel.org,
	Mailing-List fedora-kernel <kernel@lists.fedoraproject.org>,
	poma <pomidorabelisima@gmail.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Christoph Lameter <cl@linux.com>
Subject: Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()
Date: Wed, 30 Jul 2014 16:52:25 +0200	[thread overview]
Message-ID: <20140730145225.GA15757@lst.de> (raw)
In-Reply-To: <20140730122135.GE28613@hansolo.jdub.homelinux.org>

On Wed, Jul 30, 2014 at 08:21:35AM -0400, Josh Boyer wrote:
> > Thanks, I've update the author, added a Cc to ћtable and pushed it out to
> > the core-for-3.17 branch.
> 
> This fixes a bug in the 3.16 kernel.  Why wouldn't it be sent to Linus
> for inclusion in the final release there?

I'm only collecting patches for scsi, but James remains formal maintainer, so
I don't send anything to Linus.  Given that delays between me committing
things, them getting picked up by James and finally making it to Linux-next I
don't feel like another for-3.16 branch at this point is easily workable.

If James wants to cherry pick it and send it on at this time that might
still work fine, but he seems fairly busy.


  reply	other threads:[~2014-07-30 14:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53C8DF7F.5060707@gmail.com>
2014-07-18 10:57 ` WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330() poma
2014-07-18 13:21   ` Vladimir Davydov
2014-07-18 14:17     ` Christoph Hellwig
2014-07-18 20:01       ` poma
2014-07-18 20:07         ` James Bottomley
2014-07-18 20:16           ` poma
2014-07-18 21:32             ` poma
2014-07-19 16:44           ` Christoph Hellwig
2014-07-21  9:39             ` poma
2014-07-21 14:58               ` Christoph Hellwig
2014-07-21 15:38                 ` poma
2014-07-26 16:21               ` Christoph Hellwig
2014-07-26 16:44                 ` Martin K. Petersen
2014-07-27  8:09                 ` Vladimir Davydov
2014-07-28  7:49                 ` James Bottomley
2014-07-29 12:26                   ` Christoph Hellwig
2014-07-29 23:25                     ` poma
2014-07-30 12:21                     ` Josh Boyer
2014-07-30 14:52                       ` Christoph Hellwig [this message]
2014-07-30 15:04                         ` James Bottomley
2014-07-30 16:15                           ` Christoph Hellwig
2014-07-30 17:22                 ` Mike Christie
2014-07-30 17:59                   ` Christoph Hellwig
2014-07-31 13:02                     ` James Bottomley
2014-07-18 14:20   ` Christoph Lameter
2014-07-18 20:03     ` poma
2014-07-18 21:35       ` poma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140730145225.GA15757@lst.de \
    --to=hch@lst.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=cl@linux.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=kernel@lists.fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pomidorabelisima@gmail.com \
    --cc=vdavydov@parallels.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).