All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan.Cameron@huawei.com, Stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] iio: fix kernel-doc build errors" was seriously submitted to be applied to the 4.14-stable tree?
Date: Mon, 11 Dec 2017 23:20:01 +0100	[thread overview]
Message-ID: <20171211222001.GA22320@kroah.com> (raw)
In-Reply-To: <3e027e38-624d-3b44-5143-01d2fe63fc6e@infradead.org>

On Mon, Dec 11, 2017 at 02:02:18PM -0800, Randy Dunlap wrote:
> On 12/11/2017 01:14 PM, gregkh@linuxfoundation.org wrote:
> > The patch below was submitted to be applied to the 4.14-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.
> > 
> > thanks,
> > 
> > greg k-h
> 
> Mind you, I'm not pushing for its inclusion in -stable, but I would say that
> it meets all of the rules listed for inclusion, depending on how loosely or
> how strongly one interprets some of the wording there.

"Normal" build warnings/errors are great to fix, but documentation build
warnings are things I've never fixed for the stable trees before.

thanks,

greg k-h

  reply	other threads:[~2017-12-11 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 21:14 WTF: patch "[PATCH] iio: fix kernel-doc build errors" was seriously submitted to be applied to the 4.14-stable tree? gregkh
2017-12-11 22:02 ` Randy Dunlap
2017-12-11 22:20   ` Greg KH [this message]
2017-12-11 22:25   ` Greg KH
2017-12-11 22:29     ` Randy Dunlap
2017-12-12  8:19       ` Greg KH
2017-12-12  8:47         ` Jonathan Cameron

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=20171211222001.GA22320@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Stable@vger.kernel.org \
    --cc=rdunlap@infradead.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.