Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: "Kees Cook" <kees+treewide@kernel.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Stanley Chang" <stanley_chang@realtek.com>,
	"Johan Hovold" <johan+linaro@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Jinjie Ruan" <ruanjinjie@huawei.com>,
	"Rob Herring" <robh@kernel.org>,
	"Charles Han" <hanchunchao@inspur.com>,
	linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH] phy: realtek: usb: Remove const from phy_cfg allocation type
Date: Sat, 03 Oct 2026 22:49:48 +0200	[thread overview]
Message-ID: <179106058877.240943.13071215640007818125.b4-ty@kernel.org> (raw)
In-Reply-To: <20260917211303.i.538-kees@kernel.org>


On Thu, 17 Sep 2026 14:13:04 -0700, Kees Cook wrote:
> In preparation for making the devm_kmalloc family of allocators type
> aware, we need to make sure that the returned type from the allocation
> matches the type of the variable being assigned. (Before, the allocator
> would always return "void *", which can be implicitly cast to any
> pointer type.)
> 
> In both the USB2 and USB3 PHY drivers, the assigned type is
> "struct phy_cfg *", but the converted allocation type would be
> "const struct phy_cfg *", as the size was taken from the local
> "phy_cfg", which points to const as it comes from
> of_device_get_match_data(). As there is no general way to remove const
> qualifiers, take the size from the assignment target instead. No change
> in allocation size results.
> 
> [...]

Applied, thanks!

[1/1] phy: realtek: usb: Remove const from phy_cfg allocation type
      commit: 88498cfc3ce6d8ccd3080ab4cc3f394eb2754b1b

Best regards,
-- 
~Vinod



-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

      reply	other threads:[~2026-10-03 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 21:13 [PATCH] phy: realtek: usb: Remove const from phy_cfg allocation type Kees Cook
2026-10-03 20:49 ` Vinod Koul [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=179106058877.240943.13071215640007818125.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hanchunchao@inspur.com \
    --cc=johan+linaro@kernel.org \
    --cc=kees+treewide@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=ruanjinjie@huawei.com \
    --cc=stanley_chang@realtek.com \
    --cc=u.kleine-koenig@baylibre.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