From: Alexander Graf <agraf@suse.de>
To: Anton Blanchard <anton@samba.org>,
david@gibson.dropbear.id.au, aik@ozlabs.ru, paulus@samba.org
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr-vlan: Don't touch last entry in buffer list
Date: Wed, 27 Aug 2014 13:07:30 +0200 [thread overview]
Message-ID: <53FDBBF2.7040809@suse.de> (raw)
In-Reply-To: <20140822115057.443a221c@kryten>
On 22.08.14 03:50, Anton Blanchard wrote:
> The last 8 bytes of the buffer list is defined to contain the number
> of dropped frames. At the moment we use it to store rx entries,
> which trips up ethtool -S:
>
> rx_no_buffer: 9223380832981355136
>
> Fix this by skipping the last buffer list entry.
>
> Signed-off-by: Anton Blanchard <anton@samba.org>
Thanks, applied to ppc-next.
Alex
prev parent reply other threads:[~2014-08-27 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 1:50 [Qemu-devel] [PATCH] spapr-vlan: Don't touch last entry in buffer list Anton Blanchard
2014-08-26 3:02 ` David Gibson
2014-08-27 11:07 ` Alexander Graf [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=53FDBBF2.7040809@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=anton@samba.org \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).