From: David Miller <davem@davemloft•net>
To: akpm@linux-foundation•org
Cc: sfr@canb•auug.org.au, linux-next@vger•kernel.org,
linux-kernel@vger•kernel.org, dborkman@redhat•com,
netdev@vger•kernel.org, nschichan@freebox•fr
Subject: Re: linux-next: manual merge of the akpm tree with the net-next tree
Date: Wed, 22 May 2013 00:19:09 -0700 (PDT) [thread overview]
Message-ID: <20130522.001909.837849096281513655.davem@davemloft.net> (raw)
In-Reply-To: <20130522001458.af0f4ab5.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation•org>
Date: Wed, 22 May 2013 00:14:58 -0700
> On Wed, 22 May 2013 00:07:48 -0700 (PDT) David Miller <davem@davemloft•net> wrote:
>
>> From: Andrew Morton <akpm@linux-foundation•org>
>> Date: Tue, 21 May 2013 13:04:38 -0700
>>
>> > Nicolas, I think the patches need a re-check so I'll drop the versions
>> > which I presently have. Please refresh, retest and resend when
>> > convenient? It'll need to be against linux-next, which is where the
>> > conflicting (vfree/module_free) changes have occurred.
>>
>> How about working against net-next and submitting your patches to netdev
>> just like the rest of the world?
>>
>
> Well that's probably practical. But the patchset is a seccomp
> enhancement for (at present) ARM. Not exactly net stuff, or anything
> which netdev readers are likely to spend a lot of time testing and
> reviewing.
The seccomp BPF bits we reviewed and were interested in completely, because
we're going to have to support JIT'ing all of that stuff on every cpu and
we're interested how it fits into the existing BPF codes and infrastructure.
next prev parent reply other threads:[~2013-05-22 7:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 4:29 linux-next: manual merge of the akpm tree with the net-next tree Stephen Rothwell
2013-05-21 20:04 ` Andrew Morton
2013-05-22 7:07 ` David Miller
2013-05-22 7:14 ` Andrew Morton
2013-05-22 7:19 ` David Miller [this message]
2013-05-22 7:48 ` Daniel Borkmann
-- strict thread matches above, loose matches on Subject: below --
2020-06-02 9:30 Stephen Rothwell
2020-06-02 9:45 ` Stephen Rothwell
2019-07-03 10:49 Stephen Rothwell
2018-01-16 4:51 Stephen Rothwell
2017-03-20 5:10 Stephen Rothwell
2017-02-07 5:23 Stephen Rothwell
2017-02-07 8:40 ` Marc Kleine-Budde
2017-02-07 9:45 ` Stephen Rothwell
2015-05-14 7:39 Stephen Rothwell
2015-05-14 7:38 Stephen Rothwell
2014-07-23 8:18 Stephen Rothwell
2013-11-06 9:00 Stephen Rothwell
2013-11-06 8:55 Stephen Rothwell
2013-05-21 4:32 Stephen Rothwell
2013-05-21 4:25 Stephen Rothwell
2013-05-21 7:44 ` Daniel Borkmann
2013-05-21 23:54 ` Stephen Rothwell
2013-05-22 9:20 ` Daniel Borkmann
2013-05-20 4:14 Stephen Rothwell
2013-05-20 4:11 Stephen Rothwell
2013-02-20 6:02 Stephen Rothwell
2013-02-20 6:43 ` Cong Wang
2013-02-15 6:56 Stephen Rothwell
2012-06-08 3:56 Stephen Rothwell
2011-11-23 3:27 Stephen Rothwell
2011-11-23 3:40 ` Neil Horman
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=20130522.001909.837849096281513655.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=akpm@linux-foundation$(echo .)org \
--cc=dborkman@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nschichan@freebox$(echo .)fr \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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