From: Stefan Hajnoczi <stefanha@gmail.com>
To: akong@redhat.com
Cc: mst@redhat.com, kvm@vger.kernel.org, netdev@vger.kernel.org,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org,
davem@davemloft.net
Subject: Re: [PATCH v4 2/3] net: split eth_mac_addr for better error handling
Date: Mon, 21 Jan 2013 17:13:28 +0100 [thread overview]
Message-ID: <20130121161328.GE24473@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1358649789-2338-3-git-send-email-akong@redhat.com>
On Sun, Jan 20, 2013 at 10:43:08AM +0800, akong@redhat.com wrote:
> From: Stefan Hajnoczi <stefanha@gmail.com>
>
> When we set mac address, software mac address in system and hardware mac
> address all need to be updated. Current eth_mac_addr() doesn't allow
> callers to implement error handling nicely.
>
> This patch split eth_mac_addr() to prepare part and real commit part,
> then we can prepare first, and try to change hardware address, then do
> the real commit if hardware address is set successfully.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@gmail.com>
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> include/linux/etherdevice.h | 2 ++
> net/ethernet/eth.c | 43 ++++++++++++++++++++++++++++++++++++-------
> 2 files changed, 38 insertions(+), 7 deletions(-)
Feel free to make yourself author and put me just as Suggested-by:. I
posted pseudo-code but didn't write the patch or test it, so it's fair
to say that credit goes to you. :)
Stefan
next prev parent reply other threads:[~2013-01-21 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 2:43 [PATCH v4 0/3] make mac programming for virtio net more robust akong
2013-01-20 2:43 ` [PATCH v4 1/3] move virtnet_send_command() above virtnet_set_mac_address() akong
2013-01-20 2:43 ` [PATCH v4 2/3] net: split eth_mac_addr for better error handling akong
2013-01-21 4:14 ` David Miller
2013-01-21 16:13 ` Stefan Hajnoczi [this message]
2013-01-20 2:43 ` [PATCH v4 3/3] virtio-net: introduce a new control to set macaddr akong
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=20130121161328.GE24473@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=akong@redhat.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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).