From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Daniel Scally <djrscally@gmail.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 17:13:39 +0200 [thread overview]
Message-ID: <Z6tpI_zUbpXEr8qr@smile.fi.intel.com> (raw)
In-Reply-To: <1938d858-6d66-69f8-5952-9cecf133f254@linux.intel.com>
On Tue, Feb 11, 2025 at 04:32:12PM +0200, Ilpo Järvinen wrote:
> On Tue, 11 Feb 2025, Hans de Goede wrote:
...
> Currently, these don't appear in lore for some reason (not in
> patchwork)...
FWIW, lore seems down. DDoS on kernel.org? (I dunno)
> Sakari, could you please resend the series v7 so that it hopefully gets
> picked up by lore and is easier for me to apply them using the normal
> tools I've.
Usually lore picks them up when it restores. But it's up to you, of course,
how to proceed. Just my 2c.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-11 15:13 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 ` [PATCH v7 0/3] int3472: Support GPIO con_id based on _HID Andy Shevchenko
2025-02-11 10:18 ` Hans de Goede
2025-02-11 14:32 ` Ilpo Järvinen
2025-02-11 15:13 ` Andy Shevchenko [this message]
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=Z6tpI_zUbpXEr8qr@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 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.