From: David Miller <davem@davemloft.net>
To: mirq-linux@rere.qmqm.pl
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] Preparation for VLAN_TAG_PRESENT cleanup
Date: Tue, 03 Jan 2017 22:23:32 -0500 (EST) [thread overview]
Message-ID: <20170103.222332.1319598673818705870.davem@davemloft.net> (raw)
In-Reply-To: <cover.1483487429.git.mirq-linux@rere.qmqm.pl>
By submitted these in sections, but all at once, you are subverting
my requirement to submit only small self contained patch series.
Please do not do this.
The whole point is to not have a lot of patches in flight for one
thing for people to review at one time. Contributors can review
more easily small, easily digestable, pieces.
Start over, and only submit small numbers of patches at one time. Do
not submit new patches until the first series has been processed.
Thank you.
prev parent reply other threads:[~2017-01-04 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 23:53 [PATCH net-next 0/3] Preparation for VLAN_TAG_PRESENT cleanup Michał Mirosław
2017-01-03 23:53 ` [PATCH net-next 1/3] net/vlan: introduce __vlan_hwaccel_clear_tag() helper Michał Mirosław
2017-01-03 23:53 ` [PATCH net-next 3/3] net/vlan: include the shift in skb_vlan_tag_get_prio() Michał Mirosław
2017-01-03 23:53 ` [PATCH net-next 2/3] net/vlan: introduce __vlan_hwaccel_copy_tag() helper Michał Mirosław
2017-01-04 3:23 ` 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=20170103.222332.1319598673818705870.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mirq-linux@rere.qmqm.pl \
--cc=netdev@vger.kernel.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