From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-usb@vger.kernel.org,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
"open list:TEGRA ARCHITECTURE SUPPORT"
<linux-tegra@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: phy: tegra: embed UTMI pad config in phy struct
Date: Fri, 20 Nov 2026 13:40:29 +0100 [thread overview]
Message-ID: <2026112019-remote-retrieval-69b8@gregkh> (raw)
In-Reply-To: <20260921015952.1047410-1-rosenp@gmail.com>
On Sun, Sep 20, 2026 at 06:59:52PM -0700, Rosen Penev wrote:
> The UTMI pad configuration was kept in a heap-allocated void * member of
> struct tegra_usb_phy, even though the driver is the only user of the
> field. Embed the struct directly in the phy state to drop the
> allocation and the void pointer indirection. The config is
> zero-initialized when the phy struct is allocated, so no extra init
> is needed.
But why is this needed? What does this "fix"?
prev parent reply other threads:[~2026-11-20 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 1:59 Rosen Penev
2026-11-20 12:40 ` Greg Kroah-Hartman [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=2026112019-remote-retrieval-69b8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®