From: "Randy.Dunlap" <rddunlap@osdl.org>
To: werner@sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC]Add an unlocked_ioctl file operation
Date: Tue, 07 Dec 2004 12:30:48 -0800 [thread overview]
Message-ID: <41B612F8.501@osdl.org> (raw)
In-Reply-To: <200412071211.41468.werner@sgi.com>
Mike Werner wrote:
> Per Andi Kleen's suggestion.
>
> # This is a BitKeeper generated diff -Nru style patch.
> #
> # Run Lindent on ioctl.c
> # Add an ioctl path which does not take the BKL.
Isn't there some commentary around about one patch per email?
Please read
http://linux.yyz.us/patch-format.html
and
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
Also there was an email from Linus last week in the loooooong
"splitting kernel headers" thread about this. In particular,
about doing lindent patches completely standalone.
That way we can review each patch on its own merit.
Thanks.
--
~Randy
next prev parent reply other threads:[~2004-12-07 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 20:11 [RFC]Add an unlocked_ioctl file operation Mike Werner
2004-12-07 20:30 ` Randy.Dunlap [this message]
2004-12-07 21:30 ` Mike Waychison
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=41B612F8.501@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@sgi.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