From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 net-next 0/2] mvneta xmit_more and bql support
Date: Mon, 16 Jan 2017 20:13:25 -0500 (EST) [thread overview]
Message-ID: <20170116.201325.2191165766691361664.davem@davemloft.net> (raw)
In-Reply-To: <1484586512-16412-1-git-send-email-mw@semihalf.com>
From: Marcin Wojtas <mw@semihalf.com>
Date: Mon, 16 Jan 2017 18:08:30 +0100
> This is a delayed v2 of short patchset, which introduces xmit_more and BQL
> to mvneta driver. The only one change was added in xmit_more support -
> condition check preventing excessive descriptors concatenation before
> flushing in HW.
>
> Any comments or feedback would be welcome.
...
> Changelog:
> v1 -> v2:
>
> * Add checking condition that ensures too much descriptors are not
> concatenated before flushing in HW.
Looks good, series applied, thanks.
prev parent reply other threads:[~2017-01-17 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 17:08 [PATCH v2 net-next 0/2] mvneta xmit_more and bql support Marcin Wojtas
2017-01-16 17:08 ` [PATCH v2 net-next 1/2] net: mvneta: add xmit_more support Marcin Wojtas
2017-01-16 17:08 ` [PATCH v2 net-next 2/2] net: mvneta: add BQL support Marcin Wojtas
2017-01-17 1:13 ` 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=20170116.201325.2191165766691361664.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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 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).