linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Ard Biesheuvel <ardb+git@google.com>,
	linux-i2c@vger.kernel.org, stable@vger.kernel.org,
	 Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: Re: [PATCH] i2c/synquacer: Deal with optional PCLK correctly
Date: Mon, 23 Sep 2024 17:10:00 +0200	[thread overview]
Message-ID: <CAMj1kXFiYC_h_qmnOf0Vp76-hvfKcG8Z62tx-bhTKB2mj2ULaA@mail.gmail.com> (raw)
In-Reply-To: <dmwsrw6mwt3zsksxxb35qokhtf3setobeybhd34w52typxx4ld@zbjvamsqwfxt>

On Fri, 20 Sept 2024 at 11:03, Andi Shyti <andi.shyti@kernel.org> wrote:
>
> Hi Ard,
>
> On Thu, Sep 12, 2024 at 12:46:31PM GMT, Ard Biesheuvel wrote:
> > From: Ard Biesheuvel <ardb@kernel.org>
> >
> > ACPI boot does not provide clocks and regulators, but instead, provides
> > the PCLK rate directly, and enables the clock in firmware. So deal
> > gracefully with this.
> >
> > Fixes: 55750148e559 ("i2c: synquacer: Fix an error handling path in synquacer_i2c_probe()")
> > Cc: <stable@vger.kernel.org>
> > Cc: Andi Shyti <andi.shyti@kernel.org>
> > Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
>
> I'm sorry for the delay, but I needed to wait for the previous
> batch of fixes to be merged.
>
> Merged to i2c/i2c-host-next.
>

Thanks. No need to treat it with urgency on my behalf.

      reply	other threads:[~2024-09-23 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 10:46 [PATCH] i2c/synquacer: Deal with optional PCLK correctly Ard Biesheuvel
2024-09-12 17:10 ` Marion & Christophe JAILLET
2024-09-12 17:12   ` Ard Biesheuvel
2024-09-12 17:37     ` Christophe JAILLET
2024-09-20  9:03 ` Andi Shyti
2024-09-23 15:10   ` Ard Biesheuvel [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=CAMj1kXFiYC_h_qmnOf0Vp76-hvfKcG8Z62tx-bhTKB2mj2ULaA@mail.gmail.com \
    --to=ardb@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=ardb+git@google.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=linux-i2c@vger.kernel.org \
    --cc=stable@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).