public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: jejb@linux.ibm.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] scsi: support packing multi-segment in UNMAP command
Date: Tue, 22 Aug 2023 16:38:44 +0800	[thread overview]
Message-ID: <1c351e69-a187-e37a-3075-e5a4ecdc6ddd@kernel.org> (raw)
In-Reply-To: <067b15a6-1db2-719b-918d-286be4966f11@kernel.org>

On 2023/8/8 22:12, Chao Yu wrote:
> On 2023/8/8 22:04, Martin K. Petersen wrote:
>> Been working on this series to address the reported regressions. Spent
>> quite a bit of time on it last week.
> 
> Martin, thanks for the help. :)
> 
> Could you please share the report? Maybe I can join to check it.

It looks we will miss another merge window again... :(

Not sure I understand it correctly...
If this patch caused regression, could you please share the report w/ me?

Thanks,

> 
> Thanks,

  parent reply	other threads:[~2023-08-22  8:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 12:36 [PATCH v5] scsi: support packing multi-segment in UNMAP command Chao Yu
2023-03-10 14:02 ` Christoph Hellwig
2023-03-13  1:44   ` Chao Yu
2023-03-20 13:00     ` Christoph Hellwig
2023-05-17  3:49 ` Chao Yu
2023-05-22 21:51   ` Martin K. Petersen
2023-06-25  7:07     ` Chao Yu
2023-06-29  2:02       ` Martin K. Petersen
2023-06-29  2:04         ` Chao Yu
2023-07-25  9:19         ` Chao Yu
2023-08-08 13:42         ` Chao Yu
2023-08-08 14:04           ` Martin K. Petersen
2023-08-08 14:12             ` Chao Yu
2023-08-10  2:11               ` Chao Yu
2023-08-22  8:38               ` Chao Yu [this message]
2023-10-07 10:13             ` Chao Yu

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=1c351e69-a187-e37a-3075-e5a4ecdc6ddd@kernel.org \
    --to=chao@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox