linux-kernel - Re: [PATCH v3] mmc: pxamci: Simplify pxamci_probe() error handling using devm APIs

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] [day] [month] [year] [list]

Message-ID: <CAPDyKFq8jSp=JPULtKRV_fVZUh4qCvROh+MniXUhTufBWwRRaQ@mail.gmail.com>
Date: Wed, 19 Nov 2025 18:15:52 +0100
From: Ulf Hansson <ulf.hansson@...aro.org>
To: Rakuram Eswaran <rakuram.e96@...il.com>
Cc: u.kleine-koenig@...libre.com, chenhuacai@...nel.org, 
	dan.carpenter@...aro.org, david.hunter.linux@...il.com, khalid@...nel.org, 
	linux-kernel-mentees@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	linux-mmc@...r.kernel.org, lkp@...el.com, skhan@...uxfoundation.org, 
	zhoubinbin@...ngson.cn
Subject: Re: [PATCH v3] mmc: pxamci: Simplify pxamci_probe() error handling
 using devm APIs

On Wed, 19 Nov 2025 at 17:29, Rakuram Eswaran <rakuram.e96@...il.com> wrote:
>
> On Tue, 18 Nov 2025 at 21:44, Uwe Kleine-König <u.kleine-koenig@...libre.com> wrote:
> >
> > Hello Rakuram,
> >
> > On Tue, Nov 18, 2025 at 07:53:11PM +0530, Rakuram Eswaran wrote:
> > > Shall I start to send the patch to remove the redundant if condition
> > > check from pxamic_remove() function?
> > > [...]
> > > I can pull Uffe fixes branch to send the above patch? Any inputs will be
> > > really helpful to start working on this.
> >
> > It's sensible to build on top of your previous patch, yes. If you do
> > that by using next as development tree once Ulf's commit made it into
> > there, or if you apply it yourself (and then use `git format-patch
> > --base` correctly) doesn't matter much.
> >
>
> Ok, Uwe. Previous patch is already made it to linux-next branch. I will send the
> patch for this on top of next.

If you are working on mmc I strongly recommend to base your patches on top of:

git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git next

As is described in the MAINTAINERS file.

[...]

Kind regards
Uffe