public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [patch 2.6.12-rc3] modified firmware_class.c to add a new function request_firmware_nowait_nohotplug
Date: Fri, 8 Jul 2005 12:32:12 -0700	[thread overview]
Message-ID: <20050708193211.GB2228@kroah.com> (raw)
In-Reply-To: <20050709001638.GA29546@abhays.us.dell.com>

On Fri, Jul 08, 2005 at 07:16:38PM -0500, Abhay Salunke wrote:
> This is a patch which add a new function request_firmware_nowait_nohotplug 
> in firmware_calss.c  This function is exported and used by dell_rbu driver.
> It makes the file entries created by request_firmware to be agnostic to any 
> hotplug or timeout events.
> 
> Andrew , 
> Could you add this patch to the -mm tree. This patch was submitted about a
> week ago for review.

No, please do not.

> +/**
> + * request_firmware_nowait_nohotplug:
> + *
> + * Description:
> + *      Similar to request_firmware_nowait except it does not use 
> + * 	hotplug.
> + *
> + *      @cont will be called asynchronously when the firmware request is over.
> + *
> + *      @context will be passed over to @cont.
> + *
> + *      @fw may be %NULL if firmware request fails.

Wrong kerneldoc format, please fix this.

Also, why not just add the hotplug flag to the firmware structure?  That
way you don't have to add another function just to add another flag.
And you could probably get rid of the nowait version in the same way.

thanks,

greg k-h

  reply	other threads:[~2005-07-08 19:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09  0:16 [patch 2.6.12-rc3] modified firmware_class.c to add a new function request_firmware_nowait_nohotplug Abhay Salunke
2005-07-08 19:32 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-09  0:16 Abhay Salunke
2005-07-08 19:33 ` Greg KH
2005-07-08 21:12 ` randy_dunlap
2005-07-08 21:53 ` randy_dunlap
2005-07-08 21:14 Abhay_Salunke
2005-07-08 19:54 Abhay_Salunke
2005-07-08 22:24 ` 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=20050708193211.GB2228@kroah.com \
    --to=greg@kroah.com \
    --cc=Abhay_Salunke@dell.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.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