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>
Subject: Re: [PATCH v1 1/1] platform/chrome: chromeos_laptop - Remove duplicate check
Date: Tue, 1 Jul 2025 07:19:37 +0000 [thread overview]
Message-ID: <aGOMCSXpW2VQLb47@google.com> (raw)
In-Reply-To: <20250630101225.1855431-1-andriy.shevchenko@linux.intel.com>
On Mon, Jun 30, 2025 at 01:12:25PM +0300, Andy Shevchenko wrote:
> fwnode_remove_software_node() is aware of invalid input,
> no need to perform checks in the caller.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
[1/1] platform/chrome: chromeos_laptop - Remove duplicate check
commit: 0c8fe93f4e7767b0e579959de051dcaddd7197fd
Thanks!
prev parent reply other threads:[~2025-07-01 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 10:12 [PATCH v1 1/1] platform/chrome: chromeos_laptop - Remove duplicate check Andy Shevchenko
2025-07-01 7:19 ` 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=aGOMCSXpW2VQLb47@google.com \
--to=tzungbi@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--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 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 NNTP newsgroup(s).