public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giridhar Pemmasani <pgiri@yahoo.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	pgiri@yahoo.com
Subject: Re: [PATCH] Allow __vmalloc with GFP_ATOMIC
Date: Fri, 27 Apr 2007 22:48:42 -0700 (PDT)	[thread overview]
Message-ID: <730052.85710.qm@web32412.mail.mud.yahoo.com> (raw)
In-Reply-To: <4632CA04.6040706@yahoo.com.au>

--- Nick Piggin <nickpiggin@yahoo.com.au> wrote:

>> The patch below uses bh disabled lock for vmlist_lock, so
>> that __vmalloc can be used in interrupt context.

> Hi Giri,
> 
> I'm sure I've read the reason for this one before, but when you do patches
> like these, can you include that reason in the changelog please?
> 
> Thanks,
> Nick

Sorry about that. There were too many mails on this subjet and thought it
might not be good to quote them. I am quoting here the ones that matter to
this discussion. If you need more (all), let me know:

http://www.ussg.iu.edu/hypermail/linux/kernel/0605.2/1608.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0605.2/1611.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0605.2/1656.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0605.2/1779.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0605.2/1669.html

Thanks,
Giri

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  reply	other threads:[~2007-04-28  5:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28  4:03 [PATCH] Allow __vmalloc with GFP_ATOMIC Giridhar Pemmasani
2007-04-28  4:13 ` Nick Piggin
2007-04-28  5:48   ` Giridhar Pemmasani [this message]
2007-04-28  7:52 ` Russell King

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=730052.85710.qm@web32412.mail.mud.yahoo.com \
    --to=pgiri@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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