mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Angus Chen <angus.chen@jaguarmicro.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "rafael@kernel.org" <rafael@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] driver core: auxiliary bus: No need to get auxdev->dev again
Date: Wed, 19 Apr 2023 01:02:15 +0000	[thread overview]
Message-ID: <TY2PR06MB3424FD1DF9CE50F1E5AED1CB85629@TY2PR06MB3424.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <2023041816-magma-shortly-dfdd@gregkh>



> -----Original Message-----
> From: Greg KH <gregkh@linuxfoundation.org>
> Sent: Tuesday, April 18, 2023 8:32 PM
> To: Angus Chen <angus.chen@jaguarmicro.com>
> Cc: rafael@kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] driver core: auxiliary bus: No need to get auxdev->dev
> again
> 
> On Tue, Apr 18, 2023 at 08:24:06PM +0800, Angus Chen wrote:
> > Use dev variable directly.
> > No functional change intended.
> 
> Not intended, but is it really intended?  What does this line mean?
> 
> >
> > Signed-off-by: Angus Chen <angus.chen@jaguarmicro.com>
> > ---
> >  drivers/base/auxiliary.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/base/auxiliary.c b/drivers/base/auxiliary.c
> > index 4d4c2c8d26c4..ca1d044ff738 100644
> > --- a/drivers/base/auxiliary.c
> > +++ b/drivers/base/auxiliary.c
> > @@ -286,7 +286,7 @@ int auxiliary_device_init(struct auxiliary_device
> *auxdev)
> >  	}
> >
> >  	dev->bus = &auxiliary_bus_type;
> > -	device_initialize(&auxdev->dev);
> > +	device_initialize(dev);
> 
> While an interesting change, is it needed?  Why make it?
I mean it just a clean up.beacuse
struct device *dev = &auxdev->dev;
thanks.

> 
> thanks,
> 
> greg k-h

      reply	other threads:[~2023-04-19  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 12:24 Angus Chen
2023-04-18 12:32 ` Greg KH
2023-04-19  1:02   ` Angus Chen [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=TY2PR06MB3424FD1DF9CE50F1E5AED1CB85629@TY2PR06MB3424.apcprd06.prod.outlook.com \
    --to=angus.chen@jaguarmicro.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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

all inboxes | Powered by JetHome®