From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-spi@vger.kernel.org,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Andi Shyti <andi@etezian.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] spi: spi-s3c64xx: Fix system resume support
Date: Fri, 18 May 2018 09:34:11 +0100 [thread overview]
Message-ID: <20180518083411.GB24209@sirena.org.uk> (raw)
In-Reply-To: <CAJKOXPegbcXzy7QYpt09pXKcHaLji0Xyy+nmYz+wj+_awqAG4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Fri, May 18, 2018 at 07:33:03AM +0200, Krzysztof Kozlowski wrote:
> The point of resend was to add the specific cc-stable tags with a
> prerequisite for backporting:
> CC: <stable@vger.kernel.org> # 4.10.x: 1c75862d8e5a spi:
> spi-s3c64xx: Remove unused s3c64xx_spi_hwinit()
> CC: <stable@vger.kernel.org> # 4.10.x
> Unfortunately I saw that these did not end up in patch you committed.
> Mentioning required commit is, I think, quite helpful for stable guys.
If you want to mention the commit being fixed then use a Fixes: tag. I
was complaining because I'd already applied the commit before that got
resent so I had to try to figure out what was going on with it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-05-18 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180517102518eucas1p10e55ae3c884f6fe29b37c01eff0fe7a4@eucas1p1.samsung.com>
2018-05-17 10:15 ` [PATCH] spi: spi-s3c64xx: Fix system resume support Marek Szyprowski
2018-05-17 16:41 ` Mark Brown
2018-05-18 5:33 ` Krzysztof Kozlowski
2018-05-18 8:34 ` 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=20180518083411.GB24209@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andi@etezian.org \
--cc=b.zolnierkie@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=s.nawrocki@samsung.com \
--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 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.