From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org,
Klaus Kudielka <klaus.kudielka@gmail.com>,
Josua Mayer <josua@solid-run.com>
Subject: Re: [PATCH] ata: libahci_platform: Do not set mask_port_map when not needed
Date: Fri, 7 Feb 2025 09:54:03 +0100 [thread overview]
Message-ID: <Z6XKK44hE_215eoI@ryzen> (raw)
In-Reply-To: <20250207074810.1433154-1-dlemoal@kernel.org>
On Fri, Feb 07, 2025 at 04:48:10PM +0900, Damien Le Moal wrote:
> Commit 8c87215dd3a2 ("ata: libahci_platform: support non-consecutive
> port numbers") modified ahci_platform_get_resources() to allow
> identifying the ports of a controller that are defined as child nodes of
> the controller node in order to support non-consecutive port numbers (as
> defined by the platform device tree).
>
> However, this commit also erroneously sets bits 0 of
s/bits/bit/
> hpriv->mask_port_map when the platform devices tree does not define port
> child nodes, to match the fact that the temporary default number of
> ports used in that case is 1. Doing so causes ahci_platform_init_host()
> to initialize and probe only the first port, even if the controller has
> multiple ports (that are not defined through the platform DT).
>
> Fix this by removing setting bit 0 of hpriv->mask_port_map when the
> platform devices tree does not define port child nodes.
s/devices/device/
>
> Reported-by: Klaus Kudielka <klaus.kudielka@gmail.com>
> Fixes: 8c87215dd3a2 ("ata: libahci_platform: support non-consecutive port numbers")
> Cc: stable@vger.kernel.org
Cc: stable is used then the fix should be backported.
The commit referenced in Fixes: is only in v6.14-rc1, so no need to backport,
and thus no need to Cc: stable.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-02-07 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 7:48 [PATCH] ata: libahci_platform: Do not set mask_port_map when not needed Damien Le Moal
2025-02-07 8:54 ` Niklas Cassel [this message]
2025-02-07 11:35 ` Josua Mayer
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=Z6XKK44hE_215eoI@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=josua@solid-run.com \
--cc=klaus.kudielka@gmail.com \
--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 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.