public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Felipe Balbi <balbi@ti.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Sarah Sharp <sarah.a.sharp@linux.intel.com>,
	linux-usb@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/20] drivers_base: platform: use always ->name for uevent
Date: Fri, 30 Sep 2011 10:09:14 -0700	[thread overview]
Message-ID: <20110930170914.GA15341@suse.de> (raw)
In-Reply-To: <20110930132914.GA877@legolas.emea.dhcp.ti.com>

On Fri, Sep 30, 2011 at 04:29:16PM +0300, Felipe Balbi wrote:
> Hi,
> 
> On Mon, Aug 15, 2011 at 04:51:22PM +0200, Sebastian Andrzej Siewior wrote:
> > If id_entry is available then it is used. However if we remove first the
> > driver followed by the device, then the id_entry is pointing to driver's
> > memory which is long gone.
> > Since id->name and plat->name are equal there is no point in
> > distinguishing them.
> > 
> > Cc: Greg Kroah-Hartman <gregkh@suse.de>
> > Cc: Grant Likely <grant.likely@secretlab.ca>
> > Cc: linux-kernel@vger.kernel.org
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > ---
> >  drivers/base/platform.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> > index 0cad9c7..cd71575 100644
> > --- a/drivers/base/platform.c
> > +++ b/drivers/base/platform.c
> > @@ -614,7 +614,7 @@ static int platform_uevent(struct device *dev, struct kobj_uevent_env *env)
> >  		return rc;
> >  
> >  	add_uevent_var(env, "MODALIAS=%s%s", PLATFORM_MODULE_PREFIX,
> > -		(pdev->id_entry) ? pdev->id_entry->name : pdev->name);
> > +			pdev->name);
> >  	return 0;
> >  }
> >  
> 
> Just a gentle reminder on this patch. Greg, has this one been queued to
> your drivers-core tree ? Should it go on -rc or now it's already too
> late and going on merge window ?

It's been in my drivers-core tree for a while, and I didn't think it was
needed for 3.1, as it didn't solve an existing bug, did it?

It's queued for 3.2, does it need to get into 3.1-stable?  If so, I can
do that.

thanks,

greg k-h

  reply	other threads:[~2011-09-30 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1313419901-13492-1-git-send-email-bigeasy@linutronix.de>
2011-08-15 14:51 ` [PATCH 01/20] drivers_base: platform: use always ->name for uevent Sebastian Andrzej Siewior
2011-08-15 14:56   ` Grant Likely
2011-08-15 15:13     ` Sebastian Andrzej Siewior
2011-08-15 15:17       ` Grant Likely
2011-08-15 15:17       ` Grant Likely
2011-08-22 21:41         ` Sarah Sharp
2011-08-22 21:51           ` Greg KH
2011-08-23  9:50             ` Sebastian Andrzej Siewior
2011-08-23 15:32               ` Greg KH
2011-09-30 13:29   ` Felipe Balbi
2011-09-30 17:09     ` Greg KH [this message]
2011-09-30 17:40       ` Felipe Balbi
2011-09-30 17:49         ` Greg KH

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=20110930170914.GA15341@suse.de \
    --to=gregkh@suse.de \
    --cc=balbi@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox