All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Richard <thomas.richard@bootlin.com>
Cc: Peter Rosin <peda@axentia.se>,
	linux-kernel@vger.kernel.org, gregory.clement@bootlin.com,
	richard.genoud@bootlin.com, u-kumar1@ti.com,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Andrew Davis <afd@ti.com>
Subject: Re: [PATCH RESEND v3] mux: mmio: Add suspend and resume support
Date: Wed, 21 May 2025 15:46:21 +0200	[thread overview]
Message-ID: <2025052157-uncurious-crayfish-0d58@gregkh> (raw)
In-Reply-To: <8f6fb9b4-dc84-4443-b7e2-1a857400f79a@bootlin.com>

On Wed, May 21, 2025 at 02:54:04PM +0200, Thomas Richard wrote:
> On 5/21/25 14:27, Greg KH wrote:
> > On Wed, May 07, 2025 at 10:33:22AM +0200, Thomas Richard wrote:
> >> On 4/7/25 15:06, Thomas Richard wrote:
> >>> The status of each mux is read during suspend and stored in the private
> >>> memory of the mux_chip.
> >>> Then the state is restored during the resume.
> >>>
> >>> Reviewed-by: Andrew Davis <afd@ti.com>
> >>> Signed-off-by: Thomas Richard <thomas.richard@bootlin.com>
> >>
> >> Hi Greg,
> >>
> >> I apologize for involving you, but Peter is not responding anymore. I
> >> pinged him several times, resent the patch but no news.
> >>
> >> Could you please review and apply this patch directly?
> > 
> > Does not apply to my tree :(
> 
> I just tested again and it applies on v6.15-rc1.
> Which tree are you talking about ?

char-misc-next.  Or try it on linux-next, 6.15-rc1 is quite old now.

thanks,

greg k-h

      reply	other threads:[~2025-05-21 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 13:06 [PATCH RESEND v3] mux: mmio: Add suspend and resume support Thomas Richard
2025-05-07  8:33 ` Thomas Richard
2025-05-21 12:27   ` Greg KH
2025-05-21 12:54     ` Thomas Richard
2025-05-21 13:46       ` Greg KH [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=2025052157-uncurious-crayfish-0d58@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=afd@ti.com \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=richard.genoud@bootlin.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas.richard@bootlin.com \
    --cc=u-kumar1@ti.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.