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>,
	Steffen Maier <maier@linux.ibm.com>
Subject: linux-next: Fixes tag needs some work in the scsi-fixes tree
Date: Wed, 30 Jan 2019 07:53:36 +1100	[thread overview]
Message-ID: <20190130075336.3164fcc8@canb.auug.org.au> (raw)

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

Hi all,

In commit

  b63195698dea ("scsi: zfcp: fix sysfs block queue limit output for max_segment_size")

Fixes tag

  Fixes: 50c2e9107f ("scsi: introduce a max_segment_size host_template parameters")

has these problem(s):

  - SHA1 should be at least 12 digits long

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-01-29 20:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 20:53 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-03  8:47 linux-next: Fixes tag needs some work in the scsi-fixes tree Stephen Rothwell
2020-09-04  1:51 ` Martin K. Petersen
2020-06-24  7:07 Stephen Rothwell
2020-06-24  7:14 ` SeongJae Park
2020-06-24  7:23   ` Stephen Rothwell
2020-05-08 11:33 Stephen Rothwell
2020-05-11 23:54 ` Martin K. Petersen
2019-02-05 20:20 Stephen Rothwell
2019-02-06  3:55 ` Vaibhav Jain
2019-02-06  4:34   ` Stephen Rothwell
2019-02-06 13:03   ` Martin K. Petersen
2019-01-23  5:34 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=20190130075336.3164fcc8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maier@linux.ibm.com \
    --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.