All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mike Rapoport <mike.rapoport@gmail.com>
Cc: Johnny Kim <johnny.kim@atmel.com>,
	Rachel Kim <rachel.kim@atmel.com>,
	Chris Park <chris.park@atmel.com>, Tony Cho <tony.cho@atmel.com>,
	Glen Lee <glen.lee@atmel.com>, Leo Kim <leo.kim@atmel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] staging: wilc1000: remove kmalloc wrappers
Date: Fri, 11 Sep 2015 19:34:27 -0700	[thread overview]
Message-ID: <20150912023427.GA32109@kroah.com> (raw)
In-Reply-To: <1441880877-3832-1-git-send-email-mike.rapoport@gmail.com>

On Thu, Sep 10, 2015 at 01:27:52PM +0300, Mike Rapoport wrote:
> The wilc_memory.[ch] provide wrappers to kmalloc that effectively boil down to
> calling to kmalloc with flags=GFP_ATOMIC. Replacing the calls to these wrappers
> with direct calls to kmalloc allows removal of the wilc_memory.[ch] files.

These were done just before you sent them in, sorry.

      parent reply	other threads:[~2015-09-12  4:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 10:27 [PATCH 0/5] staging: wilc1000: remove kmalloc wrappers Mike Rapoport
2015-09-10 10:27 ` [PATCH 1/5] staging: wilc1000: host_interface.c: replace WILC_MALLOC with kmalloc Mike Rapoport
2015-09-11 10:55   ` Sudip Mukherjee
2015-09-12  2:33   ` Greg Kroah-Hartman
2015-09-10 10:27 ` [PATCH 2/5] staging: wilc1000: wilc_wfi_cfgoperations.c: " Mike Rapoport
2015-09-10 10:27 ` [PATCH 3/5] staging: wilc1000: do not include wilc_memory.h Mike Rapoport
2015-09-10 10:27 ` [PATCH 4/5] staging: wilc1000: make: remove wilc_memory.o from wilc1000-objs Mike Rapoport
2015-09-10 10:27 ` [PATCH 5/5] staging: wilc1000: remove wilc_memory.[ch] Mike Rapoport
2015-09-12  2:34 ` Greg Kroah-Hartman [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=20150912023427.GA32109@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris.park@atmel.com \
    --cc=glen.lee@atmel.com \
    --cc=johnny.kim@atmel.com \
    --cc=leo.kim@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.rapoport@gmail.com \
    --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 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.