From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Igor Pylypiv <ipylypiv@google.com>
Cc: Jack Wang <jinpu.wang@cloud.ionos.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Vishakha Channapattan <vishakhavc@google.com>,
Changyuan Lyu <changyuanl@google.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/4] small pm80xx cleanups and fixes
Date: Thu, 18 Nov 2021 21:50:02 -0500 [thread overview]
Message-ID: <yq1lf1k7tbh.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20211101232825.2350233-1-ipylypiv@google.com> (Igor Pylypiv's message of "Mon, 1 Nov 2021 16:28:21 -0700")
Igor,
> Igor Pylypiv (4):
> scsi: pm80xx: Apply byte mask for phy id in mpi_phy_start_resp()
> scsi: pm80xx: Do not check the address-of value for NULL
> scsi: pm80xx: Update WARN_ON check in pm8001_mpi_build_cmd()
> scsi: pm80xx: Use bitmap_zalloc() for tags bitmap allocation
Applied to 5.17/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-11-19 2:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 23:28 [PATCH 0/4] small pm80xx cleanups and fixes Igor Pylypiv
2021-11-01 23:28 ` [PATCH 1/4] scsi: pm80xx: Apply byte mask for phy id in mpi_phy_start_resp() Igor Pylypiv
2021-11-02 7:04 ` Jinpu Wang
2021-11-01 23:28 ` [PATCH 2/4] scsi: pm80xx: Do not check the address-of value for NULL Igor Pylypiv
2021-11-02 7:06 ` Jinpu Wang
2021-11-01 23:28 ` [PATCH 3/4] scsi: pm80xx: Update WARN_ON check in pm8001_mpi_build_cmd() Igor Pylypiv
2021-11-02 7:07 ` Jinpu Wang
2021-11-01 23:28 ` [PATCH 4/4] scsi: pm80xx: Use bitmap_zalloc() for tags bitmap allocation Igor Pylypiv
2021-11-02 7:08 ` Jinpu Wang
2021-11-19 2:50 ` Martin K. Petersen [this message]
2021-11-23 3:49 ` [PATCH 0/4] small pm80xx cleanups and fixes 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=yq1lf1k7tbh.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=changyuanl@google.com \
--cc=ipylypiv@google.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-scsi@vger.kernel.org \
--cc=vishakhavc@google.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.