Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <mkp@kernel.org>
To: yangxingui <yangxingui@huawei.com>
Cc: <mkp@kernel.org>,  <jejb@linux.ibm.com>,  <john.garry@linux.dev>,
	<yanaijie@huawei.com>,  <linux-scsi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,  <linuxarm@huawei.com>,
	<liuyonglong@huawei.com>,  <kangfenglong@huawei.com>
Subject: Re: [PATCH v3 0/4] scsi: hisi_sas: Some misc fixes
Date: Wed, 14 Oct 2026 22:26:38 -0400	[thread overview]
Message-ID: <yq1ik33em3v.fsf@mail.kernel.org> (raw)
In-Reply-To: <51d44015-cbbf-ab69-47ed-0c9b397da203@huawei.com>


> Could you let us know whether this series is fine to be merged as is,
> and how you would prefer the pre-existing findings to be handled: in a
> follow-up series, or folded into this one?

Please send follow-up patches.

Thanks!

-- 
Martin K. Petersen

  reply	other threads:[~2026-10-15  2:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  3:32 [PATCH v3 0/4] scsi: hisi_sas: Some misc fixes Xingui Yang
2026-10-09  3:32 ` [PATCH v3 1/4] scsi: libsas: Fix out-of-bounds memcpy in sas_ssp_task_response() Xingui Yang
2026-10-09  4:05   ` sashiko-bot
2026-10-09  3:32 ` [PATCH v3 2/4] scsi: hisi_sas: Fix incorrect delay values from magic-number cleanup Xingui Yang
2026-10-09  4:00   ` sashiko-bot
2026-10-09  3:32 ` [PATCH v3 3/4] scsi: hisi_sas: Clear PHY error counts on phyup Xingui Yang
2026-10-09  4:04   ` sashiko-bot
2026-10-09  3:32 ` [PATCH v3 4/4] scsi: hisi_sas: Fix spinup failure for SAS SSP devices in Active_Wait state Xingui Yang
2026-10-09  3:58   ` sashiko-bot
2026-10-09  7:13     ` yangxingui
2026-10-09  9:08 ` [PATCH v3 0/4] scsi: hisi_sas: Some misc fixes yangxingui
2026-10-15  2:26   ` Martin K. Petersen [this message]
2026-10-15  3:51     ` yangxingui
2026-10-15  2:25 ` 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=yq1ik33em3v.fsf@mail.kernel.org \
    --to=mkp@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=john.garry@linux.dev \
    --cc=kangfenglong@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=yanaijie@huawei.com \
    --cc=yangxingui@huawei.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