From: Matthew Wilcox <matthew@wil.cx>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: mpm@selenic.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Random number driver: make random_ioctl as an unlocked_ioctl function
Date: Fri, 11 Jan 2008 14:01:02 +0000 [thread overview]
Message-ID: <20080111140101.GL18741@parisc-linux.org> (raw)
In-Reply-To: <1200051592.3844.63.camel@nikanth-laptop.blr.novell.com>
On Fri, Jan 11, 2008 at 05:09:52PM +0530, Nikanth Karthikesan wrote:
> The random_ioctl is registered as an ioctl function but it does not
> require BKL to be held when called. Changing it as an unlocked_ioctl
> function.
>
> Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
Acked-by: Matthew Wilcox <willy@linux.intel.com>
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: mpm@selenic.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Random number driver: make random_ioctl as an unlocked_ioctl function
Date: Fri, 11 Jan 2008 07:01:02 -0700 [thread overview]
Message-ID: <20080111140101.GL18741@parisc-linux.org> (raw)
In-Reply-To: <1200051592.3844.63.camel@nikanth-laptop.blr.novell.com>
On Fri, Jan 11, 2008 at 05:09:52PM +0530, Nikanth Karthikesan wrote:
> The random_ioctl is registered as an ioctl function but it does not
> require BKL to be held when called. Changing it as an unlocked_ioctl
> function.
>
> Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
Acked-by: Matthew Wilcox <willy@linux.intel.com>
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-01-11 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 11:39 [PATCH] Random number driver: make random_ioctl as an unlocked_ioctl function Nikanth Karthikesan
2008-01-11 11:51 ` [PATCH] Random number driver: make random_ioctl as an Nikanth Karthikesan
2008-01-11 14:01 ` Matthew Wilcox [this message]
2008-01-11 14:01 ` [PATCH] Random number driver: make random_ioctl as an unlocked_ioctl function Matthew Wilcox
2008-01-11 17:17 ` [PATCH] Random number driver: make random_ioctl as an Matt Mackall
2008-01-11 17:17 ` [PATCH] Random number driver: make random_ioctl as an unlocked_ioctl function Matt Mackall
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=20080111140101.GL18741@parisc-linux.org \
--to=matthew@wil.cx \
--cc=kernel-janitors@vger.kernel.org \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.