From: Mark Brown <broonie@kernel.org>
To: Emil Renner Berthing <kernel@esmil.dk>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
linux-spi@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Vicente Bergas <vicencb@gmail.com>
Subject: Re: Applied "spi: rockchip: turn down tx dma bursts" to the spi tree
Date: Wed, 5 Jun 2019 20:55:11 +0100 [thread overview]
Message-ID: <20190605195511.GX2456@sirena.org.uk> (raw)
In-Reply-To: <CANBLGcxiXR7KqKn4U-2PgefuxpBFX=yR06cw6A5GEALuqa54FA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Wed, Jun 05, 2019 at 09:36:44PM +0200, Emil Renner Berthing wrote:
> On Wed, 8 May 2019 at 12:34, Mark Brown <broonie@kernel.org> wrote:
> > spi: rockchip: turn down tx dma bursts
> I've tried looking in the for-next and for-5.x branches here, and I
> can't seem to find this patch.
> Am I missing something?
> It fixes a problem introduced in 4.19, so it'd be nice if it could
> make it to stable trees eventually.
47300728fb213486a830565d2af49da967c9d16a is in my tree. When it reaches
Linus' tree send a request to Greg for it to be backported if none of
the stable automation picks it up.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-05 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 10:53 [PATCH] spi: rockchip: turn down tx dma bursts Emil Renner Berthing
2019-05-08 10:33 ` Applied "spi: rockchip: turn down tx dma bursts" to the spi tree Mark Brown
2019-06-05 19:36 ` Emil Renner Berthing
2019-06-05 19:55 ` Mark Brown [this message]
2019-06-05 20:14 ` Emil Renner Berthing
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=20190605195511.GX2456@sirena.org.uk \
--to=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@esmil.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vicencb@gmail.com \
/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
all inboxes | Powered by JetHome®