From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
Benson Leung <bleung@chromium.org>,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
Jameson Thies <jthies@google.com>,
Andrei Kuchynski <akuchynski@chromium.org>
Subject: Re: [PATCH v1 0/2] platform/chrome: cros_typec_switch: Fix fwnode and _ADR handling
Date: Wed, 21 Jan 2026 04:41:56 +0000 [thread overview]
Message-ID: <aXBZFMNA02PhtpPF@google.com> (raw)
In-Reply-To: <20260120131413.1697891-1-andriy.shevchenko@linux.intel.com>
On Tue, Jan 20, 2026 at 02:12:29PM +0100, Andy Shevchenko wrote:
> While looking for something else, I have noticed a nasty use of the private
> field of struct fwnode_handle in basically the only driver. So, hence the
> fix and one following cleanup.
>
> Andy Shevchenko (2):
> platform/chrome: cros_typec_switch: Don't touch struct
> fwnode_handle::dev
> platform/chrome: cros_typec_switch: simplify code with
> acpi_get_local_u64_address()
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
[1/2] platform/chrome: cros_typec_switch: Don't touch struct fwnode_handle::dev
commit: e1adf48853bc715f4deea074932aa1c44eb7abea
[2/2] platform/chrome: cros_typec_switch: simplify code with acpi_get_local_u64_address()
commit: a4065662998fbee4a0ca9886b9aa50aa9694e0e7
Thanks!
prev parent reply other threads:[~2026-01-21 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 13:12 [PATCH v1 0/2] platform/chrome: cros_typec_switch: Fix fwnode and _ADR handling Andy Shevchenko
2026-01-20 13:12 ` [PATCH v1 1/2] platform/chrome: cros_typec_switch: Don't touch struct fwnode_handle::dev Andy Shevchenko
2026-01-20 13:12 ` [PATCH v1 2/2] platform/chrome: cros_typec_switch: simplify code with acpi_get_local_u64_address() Andy Shevchenko
2026-01-21 4:41 ` Tzung-Bi Shih [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=aXBZFMNA02PhtpPF@google.com \
--to=tzungbi@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=jthies@google.com \
--cc=linux-kernel@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.