linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [2/2] powerpc/powernv: Add more BPF in defconfig
Date: Fri, 10 Feb 2017 00:17:53 +1100 (AEDT)	[thread overview]
Message-ID: <3vJzCP0mFPz9s7Z@ozlabs.org> (raw)
In-Reply-To: <20170207180641.31912-1-naveen.n.rao@linux.vnet.ibm.com>

On Tue, 2017-02-07 at 18:06:41 UTC, "Naveen N. Rao" wrote:
> On 2017/02/07 10:00PM, Michael Ellerman wrote:
> > 
> > I'll mush the patches all together and turn them all on across
> > pseries/ppc64/powernv.
> 
> Here's a version that does that. I have merged all the patches
> (including UPROBE_EVENT since that is very useful with bcc anyway). I
> have also added CGROUP_BPF to get namespace coverage.
> 
> Thanks,
> Naveen
> ---
> powerpc: include bpf/bcc related config options in defconfigs
> 
> Specifically:
> - CONFIG_BPF_SYSCALL
> - CONFIG_NET_SCHED
> - CONFIG_NET_CLS_BPF
> - CONFIG_NET_CLS_ACT
> - CONFIG_NET_ACT_BPF
> - CONFIG_CGROUP_BPF
> - CONFIG_UPROBE_EVENT
> 
> ... in pseries, ppc64 and powernv defconfigs.
> 
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/63b2547b155de2c41d40ea75015574

cheers

  reply	other threads:[~2017-02-09 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  2:55 [PATCH 1/2] powerpc/powernv: Add XHCI and USB storage to defconfig Michael Neuling
2017-02-06  2:55 ` [PATCH 2/2] powerpc/powernv: Add more BPF in defconfig Michael Neuling
2017-02-07  0:10   ` Michael Ellerman
2017-02-07  7:54     ` Naveen N. Rao
2017-02-07 11:00       ` Michael Ellerman
2017-02-07 18:06         ` Naveen N. Rao
2017-02-09 13:17           ` Michael Ellerman [this message]
2017-02-09 13:17 ` [1/2] powerpc/powernv: Add XHCI and USB storage to defconfig 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=3vJzCP0mFPz9s7Z@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=naveen.n.rao@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).