From: David Miller <davem@davemloft.net>
To: tklauser@distanz.ch
Cc: netdev@vger.kernel.org, starvik@axis.com, jesper.nilsson@axis.com
Subject: Re: [PATCH] net: cris/eth_v10: Use net_device_stats from struct net_device_stats
Date: Mon, 06 Dec 2010 13:25:23 -0800 (PST) [thread overview]
Message-ID: <20101206.132523.115937711.davem@davemloft.net> (raw)
In-Reply-To: <1291310525-6101-1-git-send-email-tklauser@distanz.ch>
From: Tobias Klauser <tklauser@distanz.ch>
Date: Thu, 2 Dec 2010 18:22:05 +0100
> struct net_device has its own struct net_device_stats member, so use
> this one instead of a private copy in struct net_local.
>
> Note: This patch was not even compile tested.
>
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Applied.
prev parent reply other threads:[~2010-12-06 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 17:22 [PATCH] net: cris/eth_v10: Use net_device_stats from struct net_device_stats Tobias Klauser
2010-12-06 21:25 ` 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=20101206.132523.115937711.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jesper.nilsson@axis.com \
--cc=netdev@vger.kernel.org \
--cc=starvik@axis.com \
--cc=tklauser@distanz.ch \
/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).