From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: "Daniel Scally" <djrscally@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl,
linux-media@vger.kernel.org
Subject: Re: [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID
Date: Tue, 11 Feb 2025 12:06:16 +0200 [thread overview]
Message-ID: <Z6shGGy2FPVc5mEK@smile.fi.intel.com> (raw)
In-Reply-To: <20250211072841.7713-1-sakari.ailus@linux.intel.com>
On Tue, Feb 11, 2025 at 09:28:38AM +0200, Sakari Ailus wrote:
> One patch turned into a set, the second patch being the original one.
>
> since v6:
>
> - Reword the comment regarding GPIO map processing.
Hans, Ilpo, I think this is in good enough shape
(the order of the checks I'm still not happy about
we can amend later on if required). Can it be taken?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-11 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 7:28 [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 1/3] platform/x86: int3472: Use correct type for "polarity", call it gpio_flags Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 2/3] platform/x86: int3472: Call "reset" GPIO "enable" for INT347E Sakari Ailus
2025-02-11 7:28 ` [PATCH v7 3/3] platform/x86: int3472: Call "func" "con_id" instead Sakari Ailus
2025-02-11 10:06 ` Andy Shevchenko [this message]
2025-02-11 10:18 ` [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Hans de Goede
2025-02-11 14:32 ` Ilpo Järvinen
2025-02-11 15:13 ` Andy Shevchenko
2025-02-11 17:12 ` Sakari Ailus
2025-02-11 17:28 ` Ilpo Järvinen
2025-02-11 17:45 ` Sakari Ailus
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=Z6shGGy2FPVc5mEK@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.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