From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Martin Wilck <mwilck@suse.com>,
Christoph Hellwig <hch@infradead.org>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
linux-scsi@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH 1/1] mpt3sas: Remove usage of dma_get_required_mask api
Date: Mon, 06 Mar 2023 20:39:55 -0500 [thread overview]
Message-ID: <yq1sfehmjnb.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <9aa5e89f-6579-15e5-cc51-d226b5d4bea3@leemhuis.info> (Thorsten Leemhuis's message of "Mon, 27 Feb 2023 15:07:45 +0100")
Thorsten,
> This afaics is a reasonable request for 6.1, as this seems to be
> (Salvatore, please correct me if I'm wrong) a regression caused by
> 0e0747de0ea3 ("scsi: mpt3sas: Fix return value check of
> dma_get_required_mask()"), which was merged for 6.0-rc7. Hence allow
> me to ask:
This had me confused, the above SHA is incorrect. It's:
e0e0747de0ea ("scsi: mpt3sas: Fix return value check of dma_get_required_mask()")
> Sreekanth and Martin, is there a reason why this request (and the
> earlier one a month ago) was apparently met with silence? Or was
> progress made in between and I just missed it?
There are three recent commit in this area. e0e0747de0ea was
accidentally reverted by Linus during a merge and reinstated as
1a2dcbdde82e. So unless I'm missing something, the appropriate thing
would be to backport these three commits:
9df650963bf6 ("scsi: mpt3sas: Don't change DMA mask while reallocating pools")
1a2dcbdde82e ("scsi: mpt3sas: re-do lost mpt3sas DMA mask fix")
06e472acf964 ("scsi: mpt3sas: Remove usage of dma_get_required_mask() API")
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-03-07 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 9:16 [PATCH 0/1] mpt3sas: Remove usage of dma_get_required_mask api Sreekanth Reddy
2022-10-28 9:16 ` [PATCH 1/1] " Sreekanth Reddy
2022-10-30 11:52 ` Christoph Hellwig
2022-10-30 11:57 ` Christoph Hellwig
2023-01-02 11:17 ` Martin Wilck
2023-01-02 13:06 ` Martin K. Petersen
2023-01-24 9:37 ` Salvatore Bonaccorso
2023-02-22 16:44 ` Salvatore Bonaccorso
2023-02-27 14:07 ` Thorsten Leemhuis
2023-03-03 9:39 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-04 9:16 ` Salvatore Bonaccorso
2023-03-07 1:39 ` Martin K. Petersen [this message]
2023-03-07 15:04 ` Martin Wilck
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=yq1sfehmjnb.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=carnil@debian.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sreekanth.reddy@broadcom.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.