From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com
Subject: Re: [net-next 0/7][pull request] ipv6: Extension header infrastructure
Date: Thu, 22 Aug 2019 16:08:10 -0700 (PDT) [thread overview]
Message-ID: <20190822.160810.90759200640693981.davem@davemloft.net> (raw)
In-Reply-To: <20190822.160144.1301428429264860069.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Thu, 22 Aug 2019 16:01:44 -0700 (PDT)
> Jeff, why are you submitting Tom's changes, can't he submit his
> patches on his own?
Just in case it isn't clear.
Tom has submitted these changes in the past, there were objections made
to them. Tom must keep submitting these changes himself and continue
the discussion if these changes are to be taken seriously.
Therefore I have tossed this submission from patchwork.
prev parent reply other threads:[~2019-08-22 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 22:59 [net-next 0/7][pull request] ipv6: Extension header infrastructure Jeff Kirsher
2019-08-22 22:59 ` [net-next 1/7] ipeh: Create exthdrs_options.c and ipeh.h Jeff Kirsher
2019-08-22 22:59 ` [net-next 2/7] ipeh: Move generic EH functions to exthdrs_common.c Jeff Kirsher
2019-08-22 22:59 ` [net-next 3/7] ipeh: Generic TLV parser Jeff Kirsher
2019-08-22 22:59 ` [net-next 4/7] ip6tlvs: Registration of TLV handlers and parameters Jeff Kirsher
2019-08-22 22:59 ` [net-next 5/7] ip6tlvs: Add TX parameters Jeff Kirsher
2019-08-22 22:59 ` [net-next 6/7] ip6tlvs: Add netlink interface Jeff Kirsher
2019-08-22 22:59 ` [net-next 7/7] ip6tlvs: Validation of TX Destination and Hop-by-Hop options Jeff Kirsher
2019-08-22 23:01 ` [net-next 0/7][pull request] ipv6: Extension header infrastructure David Miller
2019-08-22 23:08 ` 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=20190822.160810.90759200640693981.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.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