From: Niklas Cassel <cassel@kernel.org>
To: Conrad Kostecki <conikost@gentoo.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
linux-ide@vger.kernel.org, Szuying Chen <chensiying21@gmail.com>,
Jesse1_Chang@asmedia.com.tw, Richard_Hsu@asmedia.com.tw,
Chloe_Chen@asmedia.com.tw
Subject: Re: [PATCH v2] ata: ahci: Add mask_port_map module parameter
Date: Mon, 6 May 2024 18:46:19 +0200 [thread overview]
Message-ID: <ZjkJW_zx338tHmo_@ryzen.lan> (raw)
In-Reply-To: <em49d72564-1852-432d-b066-eca899af6c2a@806cd47e.com>
On Sun, May 05, 2024 at 07:42:55PM +0000, Conrad Kostecki wrote:
> Hello Niklas,
> please forgive me, I wasn't able to answer earlier. I have to roll back here
> :-)
No worries :)
> I don't know, what I exactly did wrong, but I did now tested again PATCH v2
> and can confirm, it just works as it should.
> Tested on 6.8.9 and also 6.9-rc6 (with has PATCH v2 applied).
>
> My ports are being correct masked and DUMMY is being correctly shown.
> So all fine and I am happy with the patch as it is now.
>
> Sorry for the noise, I am really not sure, what I did wrong during first
> testing.
I'm glad that the patch/kernel module param works for you.
(Even if we can all agree that we would prefer not needing a kernel module
param at all :) )
Kind regards,
Niklas
prev parent reply other threads:[~2024-05-06 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 12:51 [PATCH v2] ata: ahci: Add mask_port_map module parameter Damien Le Moal
2024-04-05 13:10 ` Niklas Cassel
2024-04-05 13:14 ` Niklas Cassel
2024-04-05 22:53 ` Conrad Kostecki
2024-04-08 0:47 ` Damien Le Moal
2024-04-08 2:26 ` Damien Le Moal
2024-04-14 13:14 ` Re[2]: " Conrad Kostecki
2024-04-16 23:13 ` Damien Le Moal
2024-04-16 23:29 ` Re[2]: " Conrad Kostecki
2024-04-17 17:21 ` Niklas Cassel
2024-05-05 19:42 ` Re[2]: " Conrad Kostecki
2024-05-06 16:46 ` Niklas Cassel [this message]
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=ZjkJW_zx338tHmo_@ryzen.lan \
--to=cassel@kernel.org \
--cc=Chloe_Chen@asmedia.com.tw \
--cc=Jesse1_Chang@asmedia.com.tw \
--cc=Richard_Hsu@asmedia.com.tw \
--cc=chensiying21@gmail.com \
--cc=conikost@gentoo.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).