From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dirk Behme <dirk.behme@de.bosch.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-spi <linux-spi@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: Applied "spi: sh-msiof: Fix timeout failures for TX-only DMA transfers" to the spi tree
Date: Thu, 4 Jan 2018 12:00:35 +0000 [thread overview]
Message-ID: <20180104120035.GC10774@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdVnYeQhdnJvaXWzjeH4LF_RJ_VdXMuJCjRqcPFABtveuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On Thu, Jan 04, 2018 at 09:26:31AM +0100, Geert Uytterhoeven wrote:
> On Thu, Jan 4, 2018 at 8:05 AM, Dirk Behme <dirk.behme@de.bosch.com> wrote:
> > On 03.01.2018 18:44, Mark Brown wrote:
> > Would it make sense to forward this to -stable, too?
> Yes, _after_ it has landed in Linus' tree.
> I didn't add a Fixes tag, as the fix needs changes to apply to any pre-4.13
> kernel.
> Most probably it will be picked up by stable automatically, as it has the
> magic word "Fix" in the one-line summary.
I'm also always a bit worried about just sending things on when nobody's
been complaining about problems without lots of testing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-01-04 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 17:11 [PATCH] spi: sh-msiof: Fix timeout failures for TX-only DMA transfers Geert Uytterhoeven
2018-01-03 17:44 ` Applied "spi: sh-msiof: Fix timeout failures for TX-only DMA transfers" to the spi tree Mark Brown
2018-01-04 7:05 ` Dirk Behme
2018-01-04 8:26 ` Geert Uytterhoeven
2018-01-04 12:00 ` Mark Brown [this message]
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=20180104120035.GC10774@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@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