linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Stephen Rothwell'" <sfr@canb.auug.org.au>,
	"'Martin K. Petersen'" <martin.petersen@oracle.com>
Cc: "'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 scsi-mkp tree
Date: Tue, 24 Aug 2021 12:13:59 +0530	[thread overview]
Message-ID: <002f01d798b3$6ca99520$45fcbf60$@samsung.com> (raw)
In-Reply-To: <20210824163435.429d389a@canb.auug.org.au>

Hi

> -----Original Message-----
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Sent: 24 August 2021 12:05
> To: Martin K. Petersen <martin.petersen@oracle.com>
> Cc: Alim Akhtar <alim.akhtar@samsung.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 scsi-mkp tree
> 
> Hi all,
> 
> In commit
> 
>   2b7661aa3f28 ("scsi: ufs: ufs-exynos: Fix static checker warning")
> 
> Fixes tag
> 
>   Fixes: 55f4b1f73631: "scsi: ufs: ufs-exynos: Add UFS host support for
Exynos
> SoCs"
> 
Sorry about this.
Martin,
You want me to re-send the patch or you will take care?
 
> has these problem(s):
> 
>   - missing space between the SHA1 and the subject
>     Just use
> 	git log -1 --format='Fixes: %h ("%s")'
> 
> --
> Cheers,
> Stephen Rothwell


  reply	other threads:[~2021-08-24  8:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210824063445epcas5p4ed6e40889cf8d78edd7914284b26e852@epcas5p4.samsung.com>
2021-08-24  6:34 ` linux-next: Fixes tag needs some work in the scsi-mkp tree Stephen Rothwell
2021-08-24  6:43   ` Alim Akhtar [this message]
2021-08-25  2:45   ` Martin K. Petersen
2021-11-04  4:37 Stephen Rothwell
2021-11-05  2:50 ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2020-08-18  6:11 Stephen Rothwell
2020-08-18  6:46 ` Can Guo
2019-12-20  5:19 Stephen Rothwell
2019-12-21 18:43 ` Martin K. Petersen
2019-11-19  9:28 Stephen Rothwell
2019-11-20  2:35 ` Martin K. Petersen
2019-08-29 23:40 Stephen Rothwell
2019-08-15 10:29 Stephen Rothwell
2019-08-20  1:53 ` Martin K. Petersen
2019-07-30 22:48 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='002f01d798b3$6ca99520$45fcbf60$@samsung.com' \
    --to=alim.akhtar@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --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;
as well as URLs for NNTP newsgroup(s).