From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: Mark Brown <broonie@kernel.org>,
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 09:26:31 +0100 [thread overview]
Message-ID: <CAMuHMdVnYeQhdnJvaXWzjeH4LF_RJ_VdXMuJCjRqcPFABtveuw@mail.gmail.com> (raw)
In-Reply-To: <ff4bca03-24aa-e77b-23ad-63ea01b98a2b@de.bosch.com>
Hi Dirk,
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:
>> The patch
>>
>> spi: sh-msiof: Fix timeout failures for TX-only DMA transfers
>>
>> has been applied to the spi tree at
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
>
> 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.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-01-04 8:26 UTC|newest]
Thread overview: 7+ 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 7:05 ` Dirk Behme
2018-01-04 8:26 ` Geert Uytterhoeven [this message]
2018-01-04 12:00 ` Mark Brown
2018-01-04 12:00 ` Mark Brown
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=CAMuHMdVnYeQhdnJvaXWzjeH4LF_RJ_VdXMuJCjRqcPFABtveuw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=broonie@kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=geert+renesas@glider.be \
--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 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.