From: Greg KH <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jonathan Cameron <jic23@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: WTF: patch "[PATCH] iio: adc: TI_AM335X_ADC should depend on HAS_DMA" was seriously submitted to be applied to the 4.9-stable tree?
Date: Mon, 9 Jan 2017 10:40:14 +0100 [thread overview]
Message-ID: <20170109094014.GB16094@kroah.com> (raw)
In-Reply-To: <CAMuHMdU80cCmi9_Mr2r4AHAkWEefsQZTsf_VeBY=2zYOLqpWCA@mail.gmail.com>
On Mon, Jan 09, 2017 at 10:03:31AM +0100, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Mon, Jan 9, 2017 at 9:25 AM, <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/stable_kernel_rules.txt.
>
> s@stable_kernel_rules.txt@process/stable-kernel-rules.rst@g
>
> Time to update the scripts? ;-)
Ah, yes, thanks, will go do that now.
> > 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 don't mind if you drop it, but it does fix a (obscure) build error.
It does on 4.9? Not according to the patch itself:
Fixes: f438b9da (" drivers: iio: ti_am335x_adc: add dma support")
$ git describe --contains f438b9da
v4.10-rc1~148^2~367^2~6^2
So why should this be applied to 4.9?
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-09 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 8:25 WTF: patch "[PATCH] iio: adc: TI_AM335X_ADC should depend on HAS_DMA" was seriously submitted to be applied to the 4.9-stable tree? gregkh
2017-01-09 9:03 ` Geert Uytterhoeven
2017-01-09 9:40 ` Greg KH [this message]
2017-01-09 9:45 ` Geert Uytterhoeven
2017-01-10 21:08 ` 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=20170109094014.GB16094@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=geert@linux-m68k.org \
--cc=jic23@kernel.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 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).