From: Greg KH <greg@kroah.com>
To: Abhay Salunke <Abhay_Salunke@dell.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
matt_domsch@dell.com
Subject: Re: [patch 2.6.12-rc3] Adds persistent entryies using request_firmware_nowaitManuel Estrada Sainz <ranty@debian.org>,
Date: Thu, 16 Jun 2005 11:43:12 -0700 [thread overview]
Message-ID: <20050616184312.GA11542@kroah.com> (raw)
In-Reply-To: <20050616003414.GA1814@littleblue.us.dell.com>
On Wed, Jun 15, 2005 at 07:34:14PM -0500, Abhay Salunke wrote:
> This is a patch to make the /sys/class/firmware entries persistent.
> This has been tested with dell_rbu; dell_rbu was modified to not call
> request_firmware_nowait again form the callback function.
>
> The new mechanism to make the entries persistent is as follows
> 1> echo 0 > /sys/class/firmware/timeout
> 2> echo 2 > /sys/class/firmware/xxx/loading
>
> step 1 prevents timeout to occur , step 2 makes the entry xxx persistent
>
> if we want to remove persistence then do this
> ech0 -2 > /sys/class/firmware/xxx/loading
Hm, those are some mighty "magic" numbers that will be tough for people
to realize exactly what they mean. Try adding a "persistant" file
instead.
> + /*
> + * 2005-06-15: Abhay Salunke <abhay_salunke@dell.com>
> + * Added firmware persistent when request_firmware_nowait.
> + * is called.
> + */
Don't add changelog comments to .c files. That belongs in the git tree,
not in the code itself.
Also, your use of tabs and spaces are wrong in a lot of places...
thanks,
greg k-h
prev parent reply other threads:[~2005-06-16 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 0:34 [patch 2.6.12-rc3] Adds persistent entryies using request_firmware_nowaitManuel Estrada Sainz <ranty@debian.org>, Abhay Salunke
2005-06-16 1:00 ` Andrew Morton
2005-06-16 4:01 ` Dmitry Torokhov
2005-06-16 15:26 ` [patch 2.6.12-rc3] Adds persistent entryies using request_firmware_nowait Abhay Salunke
2005-06-16 18:43 ` 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=20050616184312.GA11542@kroah.com \
--to=greg@kroah.com \
--cc=Abhay_Salunke@dell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt_domsch@dell.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