public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alexis GUILLEMET <alexis.guillemet@dunasys.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v1 2/2] pinctrl: intel: Fix wrong bypass assignment in intel_pinctrl_probe_pwm()
Date: Tue, 11 Feb 2025 14:17:49 +0200	[thread overview]
Message-ID: <Z6s_7XTW4-Y1VeSp@smile.fi.intel.com> (raw)
In-Reply-To: <ea58e549-a1ba-4508-8a70-59622f8c3ce3@dunasys.com>

On Tue, Feb 11, 2025 at 01:11:57PM +0100, Alexis GUILLEMET wrote:
> On Mon, Feb 10, 2025 at 08:44PM +0200, Andy Shevchenko wrote:

> Tested-by: Alexis GUILLEMET<alexis.guillemet@dunasys.com>

Thank you for confirming, I'm going to push this to my review and testing queue soon.
It should appear in the next (v6.15-rc1) Linux kernel.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2025-02-11 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 19:44 [PATCH v1 0/2] pinctrl: intel: Fix PWM initialisation Andy Shevchenko
2025-02-10 19:44 ` [PATCH v1 1/2] pwm: lpss: Clarify the bypass member semantics in struct pwm_lpss_boardinfo Andy Shevchenko
2025-02-10 19:44 ` [PATCH v1 2/2] pinctrl: intel: Fix wrong bypass assignment in intel_pinctrl_probe_pwm() Andy Shevchenko
     [not found]   ` <ea58e549-a1ba-4508-8a70-59622f8c3ce3@dunasys.com>
2025-02-11 12:17     ` Andy Shevchenko [this message]
2025-02-11  7:05 ` [PATCH v1 0/2] pinctrl: intel: Fix PWM initialisation Mika Westerberg

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=Z6s_7XTW4-Y1VeSp@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alexis.guillemet@dunasys.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@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=platform-driver-x86@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