From: Mark Brown <broonie@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the spi tree
Date: Mon, 19 Feb 2024 22:54:36 +0000 [thread overview]
Message-ID: <af7cfd01-c0ea-4e75-88a2-7202875650ca@sirena.org.uk> (raw)
In-Reply-To: <439d34e7-3bf9-4710-ae0d-6c2b94917c60@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
On Mon, Feb 19, 2024 at 02:48:51PM -0800, Randy Dunlap wrote:
> On 2/19/24 13:44, Stephen Rothwell wrote:
> > Fixes tag
> > Fixes: hash ("spi: Update the "master/slave" terminology in documentation")
> > has these problem(s):
> > - No SHA1 recognised
> > Maybe you meant
> > Fixes: 99769a52464d ("spi: Update the "master/slave" terminology in documentation")
> oh dear. Yes, I did.
> Mark, what do I need to do here?
Nothing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-19 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 21:44 linux-next: Fixes tag needs some work in the spi tree Stephen Rothwell
2024-02-19 22:48 ` Randy Dunlap
2024-02-19 22:54 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 21:37 Stephen Rothwell
2026-01-13 21:41 ` Stephen Rothwell
2022-03-17 21:18 Stephen Rothwell
2022-03-18 7:10 ` Biju Das
2022-03-18 15:44 ` Mark Brown
2022-03-18 15:48 ` Biju Das
2021-05-11 22:24 Stephen Rothwell
2021-04-11 22:37 Stephen Rothwell
2021-01-11 20:36 Stephen Rothwell
2021-01-11 20:58 ` Pratyush Yadav
2021-01-11 23:00 ` Mark Brown
2019-04-01 18:12 Stephen Rothwell
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=af7cfd01-c0ea-4e75-88a2-7202875650ca@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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