[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2025052157-uncurious-crayfish-0d58@gregkh>
Date: Wed, 21 May 2025 15:46:21 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Thomas Richard <thomas.richard@...tlin.com>
Cc: Peter Rosin <peda@...ntia.se>, linux-kernel@...r.kernel.org,
gregory.clement@...tlin.com, richard.genoud@...tlin.com,
u-kumar1@...com, Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Andrew Davis <afd@...com>
Subject: Re: [PATCH RESEND v3] mux: mmio: Add suspend and resume support
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@...com>
> >>> Signed-off-by: Thomas Richard <thomas.richard@...tlin.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
Powered by blists - more mailing lists