From: David Miller <davem@davemloft.net>
To: hariprasad@chelsio.com
Cc: netdev@vger.kernel.org, nirranjan@chelsio.com
Subject: Re: [PATCH net-next] cxgb4: Introduce API for sending work requests on ctrl queue via copy
Date: Thu, 30 Jun 2016 08:22:04 -0400 (EDT) [thread overview]
Message-ID: <20160630.082204.1957002173817318052.davem@davemloft.net> (raw)
In-Reply-To: <1467171079-27193-1-git-send-email-hariprasad@chelsio.com>
From: Hariprasad Shenai <hariprasad@chelsio.com>
Date: Wed, 29 Jun 2016 09:01:19 +0530
> If the ctrl queue is full, just follows current path by allocating an
> skb. If that fails then caller will just have to handle that case as
> before.
>
> Signed-off-by: Hariprasad Shenai <hariprasad@chelsio.com>
I only want to see new interfaces added alongside the actual users
of these interfaces.
Otherwise I'm not applying the change.
prev parent reply other threads:[~2016-06-30 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 3:31 [PATCH net-next] cxgb4: Introduce API for sending work requests on ctrl queue via copy Hariprasad Shenai
2016-06-30 12:22 ` David Miller [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=20160630.082204.1957002173817318052.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.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).