From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <david.daney@cavium.com>
Cc: linux-mips@linux-mips.org, netdev@vger.kernel.org,
gregkh@suse.de, devel@driverdev.osuosl.org,
ddaney.cavm@gmail.com
Subject: Re: [PATCH] staging: octeon-ethernet: Fix compile error caused by changed to struct skb_frag_struct.
Date: Wed, 9 Nov 2011 17:17:14 +0000 [thread overview]
Message-ID: <20111109171714.GA31771@linux-mips.org> (raw)
In-Reply-To: <1320698970-1854-1-git-send-email-david.daney@cavium.com>
On Mon, Nov 07, 2011 at 12:49:30PM -0800, David Daney wrote:
> Evidently the definition of struct skb_frag_struct has changed, so we
> need to change to match it.
>
> Signed-off-by: David Daney <david.daney@cavium.com>
> ---
As usual for this drive I've applied this to the MIPS tree and will
send it to Linus in a few days unless somebody objects.
Thanks,
Ralf
prev parent reply other threads:[~2011-11-09 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 20:49 [PATCH] staging: octeon-ethernet: Fix compile error caused by changed to struct skb_frag_struct David Daney
2011-11-09 17:17 ` 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=20111109171714.GA31771@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-mips@linux-mips.org \
--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).