From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
netdev@vger.kernel.org, ast@fb.com, daniel@iogearbox.net
Subject: Re: [PATCH 1/3] powerpc: bpf: remove redundant check for non-null image
Date: Mon, 23 Jan 2017 22:44:53 +0530 [thread overview]
Message-ID: <20170123171453.GD3820@naverao1-tp.localdomain> (raw)
In-Reply-To: <20170116.133859.1157069434816521683.davem@davemloft.net>
Hi David,
On 2017/01/16 01:38PM, David Miller wrote:
>
> I'm assuming these patches will go via the powerpc tree.
>
> If you want them to go into net-next, I kindly ask that you always
> explicitly say so, and furthermore always submit a patch series with
> a proper "[PATCH 0/N] ..." header posting.
Sure. Sorry for the confusion. I will be more explicit next time.
Thanks,
Naveen
next prev parent reply other threads:[~2017-01-23 17:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 17:10 [PATCH 1/3] powerpc: bpf: remove redundant check for non-null image Naveen N. Rao
2017-01-13 17:10 ` [PATCH 2/3] powerpc: bpf: flush the entire JIT buffer Naveen N. Rao
2017-01-13 20:10 ` Alexei Starovoitov
2017-01-13 22:55 ` Daniel Borkmann
2017-01-27 0:40 ` [2/3] " Michael Ellerman
2017-01-13 17:10 ` [PATCH 3/3] powerpc: bpf: implement in-register swap for 64-bit endian operations Naveen N. Rao
2017-01-13 17:17 ` David Laight
2017-01-13 17:52 ` 'Naveen N. Rao'
2017-01-15 15:00 ` Benjamin Herrenschmidt
2017-01-23 19:22 ` 'Naveen N. Rao'
2017-01-24 16:13 ` David Laight
2017-01-24 16:25 ` 'Naveen N. Rao'
2017-01-13 20:09 ` [PATCH 1/3] powerpc: bpf: remove redundant check for non-null image Alexei Starovoitov
2017-01-16 18:38 ` David Miller
2017-01-23 17:14 ` Naveen N. Rao [this message]
2017-01-27 0:40 ` [1/3] " Michael Ellerman
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=20170123171453.GD3820@naverao1-tp.localdomain \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).