All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	John Pittman <jpittman@redhat.com>
Subject: linux-next: Fixes tag needs some work in the scsi-mkp tree
Date: Fri, 30 Aug 2019 09:40:21 +1000	[thread overview]
Message-ID: <20190830094021.5a9fa690@canb.auug.org.au> (raw)

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

Hi all,

In commit

  f18b30a01e21 ("scsi: fnic: print port speed only at driver init or speed change")

Fixes tag

  Fixes: commit d948e6383ec3 ("scsi: fnic: Add port speed stat to fnic debug stats")

has these problem(s):

  - leading word 'commit' unexpected

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-08-29 23:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 23:40 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-04  4:37 linux-next: Fixes tag needs some work in the scsi-mkp tree Stephen Rothwell
2021-11-05  2:50 ` Martin K. Petersen
     [not found] <CGME20210824063445epcas5p4ed6e40889cf8d78edd7914284b26e852@epcas5p4.samsung.com>
2021-08-24  6:34 ` Stephen Rothwell
2021-08-24  6:43   ` Alim Akhtar
2021-08-25  2:45   ` Martin K. Petersen
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-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=20190830094021.5a9fa690@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jpittman@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.