public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>
Cc: Pratyush Yadav <p.yadav@ti•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tag needs some work in the spi tree
Date: Tue, 12 Jan 2021 07:36:06 +1100	[thread overview]
Message-ID: <20210112073606.7cb02e42@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 545 bytes --]

Hi all,

In commit

  2ef0170e9039 ("spi: cadence-quadspi: Fix build warning on 32-bit platforms")

Fixes tag

  Fixes: f453f293979f ("spi: cadence-quadspi: Wait at least 500 ms for direct reads")

has these problem(s):

  - Subject does not match target commit subject
    Just use
	git log -1 --format='Fixes: %h ("%s")'

Did yu mean

Fixes: f453f293979f ("spi: cadence-quadspi: Add DTR support")

or

Fixes: 0920a32cf6f2 ("spi: cadence-quadspi: Wait at least 500 ms for direct reads")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2021-01-11 20:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 20:36 Stephen Rothwell [this message]
2021-01-11 20:58 ` linux-next: Fixes tag needs some work in the spi tree Pratyush Yadav
2021-01-11 23:00   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2026-01-13 21:37 Stephen Rothwell
2026-01-13 21:41 ` Stephen Rothwell
2024-02-19 21:44 Stephen Rothwell
2024-02-19 22:48 ` Randy Dunlap
2024-02-19 22:54   ` Mark Brown
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
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=20210112073606.7cb02e42@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=broonie@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=p.yadav@ti$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox