From: Sasha Levin <sasha.levin@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: xeb@mail.ru, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pptp: use idr for allocation of callids
Date: Thu, 5 Nov 2015 15:17:11 -0500 [thread overview]
Message-ID: <563BB947.1080008@oracle.com> (raw)
In-Reply-To: <20151105.151248.1982764713298691007.davem@davemloft.net>
On 11/05/2015 03:12 PM, David Miller wrote:
> From: Sasha Levin <sasha.levin@oracle.com>
> Date: Thu, 5 Nov 2015 15:07:44 -0500
>
>> > The current implementation used a bitfield with a corresponding array to
>> > manage assignment of call ids. Rather than open-coding it, use IDR for
>> > this.
>> >
>> > Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
> Please resubmit this when the net-next tree opens back up, thanks.
Will do, sorry.
Thanks,
Sasha
prev parent reply other threads:[~2015-11-05 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 20:07 [PATCH] pptp: use idr for allocation of callids Sasha Levin
2015-11-05 20:12 ` David Miller
2015-11-05 20:17 ` Sasha Levin [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=563BB947.1080008@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xeb@mail.ru \
/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).