From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Martin Wilck <mwilck@suse.com>
Cc: martin.petersen@oracle.com, Lee Duncan <lduncan@suse.com>,
Saurav Kashyap <skashyap@marvell.com>,
GR-QLogic-Storage-Upstream@marvell.com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/3] qedf misc bug fixes
Date: Wed, 08 May 2024 08:32:57 -0400 [thread overview]
Message-ID: <yq1wmo4wkph.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <afc8819fcc0f9acf23ecea3730203444fed99713.camel@suse.com> (Martin Wilck's message of "Wed, 08 May 2024 12:15:10 +0200")
Martin,
> Martin P., any chance to get this set applied?
The series had a test robot warning and I requested a v2 to be posted
with the fix rolled in.
https://lore.kernel.org/all/yq1h6fq8cv3.fsf@ca-mkp.ca.oracle.com/
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-05-08 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 10:05 [PATCH 0/3] qedf misc bug fixes Saurav Kashyap
2024-03-15 10:05 ` [PATCH 1/3] qedf: Don't process stag work during unload and recovery Saurav Kashyap
2024-03-15 10:05 ` [PATCH 2/3] qedf: Wait for stag work during unload Saurav Kashyap
2024-03-16 1:34 ` kernel test robot
2024-03-15 10:06 ` [PATCH 3/3] qedf: Memset qed_slowpath_params to zero before use Saurav Kashyap
2024-03-15 20:45 ` [PATCH 0/3] qedf misc bug fixes Martin Wilck
2024-05-01 22:28 ` Lee Duncan
2024-05-08 10:15 ` Martin Wilck
2024-05-08 12:32 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-17 13:53 Nilesh Javali
2022-01-19 3:39 ` Martin K. Petersen
2022-01-25 5:40 ` 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=yq1wmo4wkph.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=skashyap@marvell.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