public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: <jinpu.wang@cloud.ionos.com>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>, <linux-scsi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <hare@suse.de>,
	<damien.lemoal@opensource.wdc.com>, <Ajish.Koshy@microchip.com>
Subject: Re: [PATCH 0/4] pm8001 driver improvements
Date: Thu, 16 Jun 2022 21:45:58 -0400	[thread overview]
Message-ID: <yq1edzooyep.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1654879602-33497-1-git-send-email-john.garry@huawei.com> (John Garry's message of "Sat, 11 Jun 2022 00:46:38 +0800")


John,

> This small series includes the following:
> - Rework how some shost values are set
> - Fix a longstanding bug that the driver attempts to use tags before they
>   are configured
> - Stop using {set, clear}_bit()
> - Expose HW queues

Applied to 5.20/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2022-06-17  1:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 16:46 [PATCH 0/4] pm8001 driver improvements John Garry
2022-06-10 16:46 ` [PATCH 1/4] scsi: pm8001: Rework shost initial values John Garry
2022-06-13  6:39   ` Jinpu Wang
2022-06-10 16:46 ` [PATCH 2/4] scsi: pm8001: Setup tags before using them John Garry
2022-06-10 16:46 ` [PATCH 3/4] scsi: pm8001: Use non-atomic bitmap ops for tag alloc + free John Garry
2022-06-20  6:00   ` Hannes Reinecke
2022-06-20  6:07     ` Damien Le Moal
2022-06-20  6:53       ` Jinpu Wang
2022-06-20  7:40       ` John Garry
2022-06-10 16:46 ` [PATCH 4/4] scsi: pm8001: Expose HW queues for pm80xx hw John Garry
2022-06-13  7:28 ` [PATCH 0/4] pm8001 driver improvements Damien Le Moal
2022-06-17  1:45 ` Martin K. Petersen [this message]
2022-06-22  2:10 ` Martin K. Petersen

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=yq1edzooyep.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=Ajish.Koshy@microchip.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hare@suse.de \
    --cc=jejb@linux.ibm.com \
    --cc=jinpu.wang@cloud.ionos.com \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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