From: David Vrabel <david.vrabel@citrix.com>
To: Takashi Iwai <tiwai@suse.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
David Vrabel <david.vrabel@citrix.com>, <netdev@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen-netfront: Use static attribute groups for sysfs entries
Date: Wed, 4 Feb 2015 13:53:39 +0000 [thread overview]
Message-ID: <54D22463.4070703@citrix.com> (raw)
In-Reply-To: <1423057135-6939-1-git-send-email-tiwai@suse.de>
On 04/02/15 13:38, Takashi Iwai wrote:
> Instead of manual calls of device_create_file() and
> device_remove_files(), assign the static attribute groups to netdev
> groups array. This simplifies the code and avoids the possible
> races.
Acked-by: David Vrabel <david.vrabel@citrix.com>
David
next prev parent reply other threads:[~2015-02-04 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 13:38 [PATCH] xen-netfront: Use static attribute groups for sysfs entries Takashi Iwai
2015-02-04 13:53 ` David Vrabel [this message]
2015-02-05 8:33 ` David Miller
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=54D22463.4070703@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=xen-devel@lists.xenproject.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).