From: Ralf Baechle <ralf@linux-mips.org>
To: Greg KH <greg@kroah.com>
Cc: David Daney <david.daney@cavium.com>,
rongqing.li@windriver.com, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] staging/octeon: Software should check the checksum of no tcp/udp packets
Date: Tue, 27 Sep 2011 04:01:28 +0200 [thread overview]
Message-ID: <20110927020128.GA26048@linux-mips.org> (raw)
In-Reply-To: <20110927005127.GB10447@kroah.com>
On Mon, Sep 26, 2011 at 05:51:27PM -0700, Greg KH wrote:
> > This looks fine to me,
> >
> > Acked-by: David Daney <david.daney@cavium.com>
> >
> > I would let davem, Ralf and Greg KH fight over who gets to merge it.
>
> I'll let Ralf take it, unless he wants me to.
>
> Ralf?
Ok. Yes, that seems the best solution.
Ralf
prev parent reply other threads:[~2011-09-27 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 1:08 [PATCH] staging/octeon: Software should check the checksum of no tcp/udp packets rongqing.li
2011-09-26 19:50 ` David Daney
2011-09-27 0:51 ` Greg KH
2011-09-27 2:01 ` Ralf Baechle [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=20110927020128.GA26048@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=greg@kroah.com \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=rongqing.li@windriver.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).