linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "tony.cho" <tony.cho@atmel.com>
Cc: Chaehyun Lim <chaehyun.lim@gmail.com>,
	gregkh@linuxfoundation.org, rachel.kim@atmel.com,
	dean.lee@atmel.com, chris.park@atmel.com,
	devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
	johnny.kim@atmel.com
Subject: Re: [PATCH V2 1/3] staging: wilc1000: coreconfigurator.c: remove WILC_MALLOC
Date: Mon, 27 Jul 2015 10:52:57 +0300	[thread overview]
Message-ID: <20150727075256.GB9499@mwanda> (raw)
In-Reply-To: <55B59D8D.6010805@atmel.com>

> On 2015년 07월 24일 09:44, Dan Carpenter wrote:
> >On Fri, Jul 24, 2015 at 08:55:53AM +0900, Chaehyun Lim wrote:
> >>Use kmalloc and kmalloc_array instead of WILC_MALLOC.
> >>
> >>Signed-off-by: Chaehyun Lim <chaehyun.lim@gmail.com>
> >>---
> >>V2: Use GFP_KERNEL flag instead of GFP_ATOMIC
> >This is probably the correct thing but how did you check that we aren't
> >holding a spin_lock or in IRQ context?

Thanks for the reply Tony, but I was really just trying to see how
Chaehyun checks his patches or if they are automatically generated.

regards,
dan carpenter


  parent reply	other threads:[~2015-07-27  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 23:55 [PATCH V2 1/3] staging: wilc1000: coreconfigurator.c: remove WILC_MALLOC Chaehyun Lim
2015-07-23 23:55 ` [PATCH V3 2/3] staging: wilc1000: coreconfigurator.c: add kmalloc error check Chaehyun Lim
2015-07-23 23:55 ` [PATCH V3 3/3] staging: wilc1000: coreconfigurator.c: fix " Chaehyun Lim
2015-07-24  0:44 ` [PATCH V2 1/3] staging: wilc1000: coreconfigurator.c: remove WILC_MALLOC Dan Carpenter
     [not found]   ` <55B59D8D.6010805@atmel.com>
2015-07-27  7:52     ` Dan Carpenter [this message]
2015-07-29 20:45 ` 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=20150727075256.GB9499@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=chaehyun.lim@gmail.com \
    --cc=chris.park@atmel.com \
    --cc=dean.lee@atmel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johnny.kim@atmel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rachel.kim@atmel.com \
    --cc=tony.cho@atmel.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;
as well as URLs for NNTP newsgroup(s).