linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tomas Henzl <thenzl@redhat.com>
Subject: Re: linux-next: Fixes tag needs some work in the scsi-fixes tree
Date: Thu, 03 Sep 2020 21:51:17 -0400	[thread overview]
Message-ID: <yq1lfhqb9aj.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200903184738.53f62617@canb.auug.org.au> (Stephen Rothwell's message of "Thu, 3 Sep 2020 18:47:38 +1000")


Stephen,

>   Fixes: 320e77acb3 scsi: mpt3sas: Irq poll to avoid CPU hard lockups
>   Fixes: a6ffd5bf681 scsi: megaraid_sas: Call disable_irq from process IRQ poll

Ah, my regex missed the short SHAs due to the missing description
quotation marks. Fixed my script and fixed up the commits.

Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2020-09-04  1:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-29 20:53 Stephen Rothwell
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=yq1lfhqb9aj.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=thenzl@redhat.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 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).