linux-kernel - Re: [PATCH 9/9] regulator: dummy: convert to use the faux device interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z9guHSE0nwC1-52J@bogus>
Date: Mon, 17 Mar 2025 14:13:49 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>,
	Sudeep Holla <sudeep.holla@....com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>
Subject: Re: [PATCH 9/9] regulator: dummy: convert to use the faux device
 interface

On Mon, Mar 17, 2025 at 02:00:04PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Mar 17, 2025 at 10:13:21AM +0000, Sudeep Holla wrote:
> > From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> 
> Why are you resending my patch back to me?
> 
> > The dummy regulator driver does not need to create a platform device, it
> > only did so because it was simple to do.  Change it over to use the
> > faux bus instead as this is NOT a real platform device, and it makes
> > the code even smaller than before.
> > 
> > Reviewed-by: Mark Brown <broonie@...nel.org>
> > Reviewed-by: Jonathan Cameron <Jonathan.Cameron@...wei.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > Message-Id: <2025021027-outclass-stress-59dd@...gkh>
> > (sudeep.holla: Made dummy_regulator_driver static)
> 
> So this is a new version?
> 

Not really, I pulled your patch as I needed that as well to clean out
all faux device out of platform. I just made dummy_regulator_driver
static back again as compiler was warning. Definitely nothing new.
I will drop it when posting v2. You can probably fix up to make
dummy_regulator_driver static.

> And as was pointed out, this is already in my tree, and there's a
> conflict in linux-next with it.
> 

Ah may be I missed to pull the updated next. I see I was still on
next-20250311. Sorry for that.

-- 
Regards,
Sudeep