From: David Miller <davem@davemloft.net>
To: holzheu@linux.vnet.ibm.com
Cc: daniel@iogearbox.net, ast@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH net 1/2] bpf, s390: fix jit branch offset related to ldimm64
Date: Fri, 04 Aug 2017 10:13:28 -0700 (PDT) [thread overview]
Message-ID: <20170804.101328.1848792783426898491.davem@davemloft.net> (raw)
In-Reply-To: <20170804191033.30bd8f03@TP-holzheu>
From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Date: Fri, 4 Aug 2017 19:10:33 +0200
> At least I would vote for "Cc: stable".
No, please do not ever do this for networking patches.
next prev parent reply other threads:[~2017-08-04 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 12:20 [PATCH net 0/2] Two BPF fixes for s390 Daniel Borkmann
2017-08-04 12:20 ` [PATCH net 1/2] bpf, s390: fix jit branch offset related to ldimm64 Daniel Borkmann
2017-08-04 13:44 ` Michael Holzheu
2017-08-04 13:52 ` Daniel Borkmann
2017-08-04 17:10 ` Michael Holzheu
2017-08-04 17:13 ` David Miller [this message]
2017-08-04 12:20 ` [PATCH net 2/2] bpf, s390: fix build for libbpf and selftest suite Daniel Borkmann
2017-08-04 18:19 ` [PATCH net 0/2] Two BPF fixes for s390 David Miller
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=20170804.101328.1848792783426898491.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=holzheu@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).