All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: James Hogan <james.hogan@mips.com>
Cc: john@phrozen.org, ralf@linux-mips.org, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] MIPS: pci: Remove KERN_WARN instance inside the mt7620 driver" was seriously submitted to be applied to the 4.9-stable tree?
Date: Mon, 27 Nov 2017 13:56:49 +0100	[thread overview]
Message-ID: <20171127125649.GA13615@kroah.com> (raw)
In-Reply-To: <20171127124036.GA11276@jhogan-linux.mipstec.com>

On Mon, Nov 27, 2017 at 12:40:36PM +0000, James Hogan wrote:
> Hi Greg,
> 
> On Mon, Nov 27, 2017 at 01:35:46PM +0100, gregkh@linuxfoundation.org wrote:
> > The patch below was submitted to be applied to the 4.9-stable tree.
> > 
> > I fail to see how this patch meets the stable kernel rules as found at
> > Documentation/process/stable-kernel-rules.rst.
> > 
> > I could be totally wrong, and if so, please respond to 
> > <stable@vger.kernel.org> and let me know why this patch should be
> > applied.  Otherwise, it is now dropped from my patch queues, never to be
> > seen again.
> 
> I should have adjusted the commit message. KERN_WARN doesn't exist so it
> actually fixes a build error as well as switching to pr_warn().

What build error?  I have not heard of this breaking the build on 4.9
for the past year, is it in some config that no one uses?  :)

thanks,

greg k-h

  reply	other threads:[~2017-11-27 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 12:35 WTF: patch "[PATCH] MIPS: pci: Remove KERN_WARN instance inside the mt7620 driver" was seriously submitted to be applied to the 4.9-stable tree? gregkh
2017-11-27 12:40 ` James Hogan
2017-11-27 12:56   ` Greg KH [this message]
2017-11-27 14:13     ` James Hogan
2017-11-27 14:13       ` James Hogan
2017-11-27 15:06       ` Greg KH

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=20171127125649.GA13615@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=james.hogan@mips.com \
    --cc=john@phrozen.org \
    --cc=ralf@linux-mips.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.