From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: mika.westerberg@linux.intel.com, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] pinctrl: intel: drop repeated config dependency
Date: Mon, 3 Mar 2025 16:03:44 +0200 [thread overview]
Message-ID: <Z8W2wFlrkMK6ZP1R@smile.fi.intel.com> (raw)
In-Reply-To: <20250303135506.323533-1-raag.jadav@intel.com>
On Mon, Mar 03, 2025 at 07:25:06PM +0530, Raag Jadav wrote:
> We already have ACPI dependency for Intel pinctrl menu. No need to
> repeat it.
Makes sense to me. I'll wait for Mika's Ack on this and apply to my branch.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-03-03 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 13:55 [PATCH v1] pinctrl: intel: drop repeated config dependency Raag Jadav
2025-03-03 14:03 ` Mika Westerberg
2025-03-03 14:21 ` Andy Shevchenko
2025-03-03 14:03 ` Andy Shevchenko [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=Z8W2wFlrkMK6ZP1R@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=raag.jadav@intel.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