All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: andriy.shevchenko@linux.intel.com
Cc: stephen@networkplumber.org, bridge@lists.linux-foundation.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH v1] bridge: Switch to bitmap_zalloc()
Date: Fri, 31 Aug 2018 23:13:28 -0700 (PDT)	[thread overview]
Message-ID: <20180831.231328.2014260442176283292.davem@davemloft.net> (raw)
In-Reply-To: <20180830103318.60804-1-andriy.shevchenko@linux.intel.com>

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Thu, 30 Aug 2018 13:33:18 +0300

> Switch to bitmap_zalloc() to show clearly what we are allocating.
> Besides that it returns pointer of bitmap type instead of opaque void *.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Applied to net-next, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: andriy.shevchenko@linux.intel.com
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [Bridge] [PATCH v1] bridge: Switch to bitmap_zalloc()
Date: Fri, 31 Aug 2018 23:13:28 -0700 (PDT)	[thread overview]
Message-ID: <20180831.231328.2014260442176283292.davem@davemloft.net> (raw)
In-Reply-To: <20180830103318.60804-1-andriy.shevchenko@linux.intel.com>

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Thu, 30 Aug 2018 13:33:18 +0300

> Switch to bitmap_zalloc() to show clearly what we are allocating.
> Besides that it returns pointer of bitmap type instead of opaque void *.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Applied to net-next, thanks.

  reply	other threads:[~2018-09-01 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 10:33 [PATCH v1] bridge: Switch to bitmap_zalloc() Andy Shevchenko
2018-08-30 10:33 ` [Bridge] " Andy Shevchenko
2018-09-01  6:13 ` David Miller [this message]
2018-09-01  6:13   ` David Miller

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=20180831.231328.2014260442176283292.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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.