From: Greg KH <greg@kroah.com>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH 02/02] USB: add dynamic id functionality to USB core
Date: Thu, 17 Nov 2005 17:39:04 -0800 [thread overview]
Message-ID: <20051118013904.GA11916@kroah.com> (raw)
In-Reply-To: <200511172058.48797.ioe-lkml@rameria.de>
On Thu, Nov 17, 2005 at 08:58:42PM +0100, Ingo Oeser wrote:
> Hi,
>
> On Thursday 17 November 2005 17:25, Greg KH wrote:
> > On Thu, Nov 17, 2005 at 10:55:33AM -0500, Alan Stern wrote:
> > > On Wed, 16 Nov 2005, Greg KH wrote:
> > > > +static int usb_create_newid_file(struct usb_driver *usb_drv)
> > > > +{
> > > > + int error = 0;
> > > > +
> > > > + if (usb_drv->probe != NULL)
> > > > + error = sysfs_create_file(&usb_drv->driver.kobj,
> > > > + &driver_attr_new_id.attr);
> > > > + return error;
> > > > +}
> > >
> > > This deserves to be an inline function.
>
> Come on, this is just a gloryfied if :-)
>
> static inline int usb_create_newid_file(struct usb_driver *usb_drv)
> {
> if (usb_drv->probe != NULL) {
> return sysfs_create_file(&usb_drv->driver.kobj,
> &driver_attr_new_id.attr);
> } else {
> return 0;
> }
> }
Yes it is. But it's an #ifdef if, which makes it want to be a separate
function.
thanks,
greg k-h
prev parent reply other threads:[~2005-11-18 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 0:30 [PATCH 00/02] [RFC] Add dynamic id support to all USB drivers Greg KH
2005-11-17 0:31 ` [PATCH 01/02] USB: reorg some functions out of the main usb.c file Greg KH
2005-11-17 0:32 ` [PATCH 02/02] USB: add dynamic id functionality to USB core Greg KH
2005-11-17 15:55 ` [linux-usb-devel] " Alan Stern
2005-11-17 16:25 ` Greg KH
2005-11-17 17:19 ` Alan Stern
2005-11-18 1:09 ` Greg KH
2005-11-17 19:58 ` Ingo Oeser
2005-11-18 1:39 ` Greg KH [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=20051118013904.GA11916@kroah.com \
--to=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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