From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: hadi@cyberus.ca, jpirko@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] net sched: make pedit check for clones instead
Date: Mon, 07 Jun 2010 01:09:58 -0700 (PDT) [thread overview]
Message-ID: <20100607.010958.149821476.davem@davemloft.net> (raw)
In-Reply-To: <20100604130511.GA10925@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 4 Jun 2010 23:05:11 +1000
> On Fri, Jun 04, 2010 at 08:43:06AM -0400, jamal wrote:
>> And here's the second one. I noticed Changli's changes are not yet in
>> net-next. I will wait for that change to propagate and then send the
>> fix to pedit that i discussed with Herbert.
>
> Thanks Jamal!
>
> BTW, I think this patch should go in first (before the one that
> removes the OK2MUNGE setting) to be on the safe side.
I applied them this way to net-next-2.6, thanks!
prev parent reply other threads:[~2010-06-07 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 12:43 [PATCH net-next-2.6] net sched: make pedit check for clones instead jamal
2010-06-04 13:05 ` Herbert Xu
2010-06-07 8:09 ` 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=20100607.010958.149821476.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--cc=jpirko@redhat.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).