All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peng.hao2@zte.com.cn, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] kvm: x86: fix a compile warning" was seriously submitted to be applied to the 4.16-stable tree?
Date: Tue, 17 Apr 2018 14:54:59 +0200	[thread overview]
Message-ID: <20180417125459.GA5245@kroah.com> (raw)
In-Reply-To: <33d6621f-ef78-cd1c-662c-3ea13884f7b9@redhat.com>

On Tue, Apr 17, 2018 at 02:46:01PM +0200, Paolo Bonzini wrote:
> On 17/04/2018 14:19, gregkh@linuxfoundation.org wrote:
> > The patch below was submitted to be applied to the 4.16-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.
> 
> There are people compiling with -Werror.  But really, I sometimes wonder
> if stable-kernel-rules.rst should be perused in the same way as the GNU
> coding standards].  Most patches that are "auto-selected" these days are
> (at least for KVM) exactly the "This could be a problem..." type of thing
> that is singled out as _not_ stable-worthy.

Are you sure -Werror shows this?  And it's not just a sparse "warning"?

I want to fix "normal" build warnings, ones that show up with out having
to override any options. That way we catch real problems if they show
up.  To try to fix up warnings that no one will ever see is just
pointless for stable trees.

thanks,

greg k-h

  reply	other threads:[~2018-04-17 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 12:19 WTF: patch "[PATCH] kvm: x86: fix a compile warning" was seriously submitted to be applied to the 4.16-stable tree? gregkh
2018-04-17 12:46 ` Paolo Bonzini
2018-04-17 12:54   ` Greg KH [this message]
2018-04-17 14:10     ` Paolo Bonzini
2018-04-17 14:19       ` Greg KH
2018-04-17 12:46 ` Paolo Bonzini

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=20180417125459.GA5245@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=pbonzini@redhat.com \
    --cc=peng.hao2@zte.com.cn \
    --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.