From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, <david.vrabel@citrix.com>,
<boris.ostrovsky@oracle.com>, Juergen Gross <JGross@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, <netdev@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen-netfront: prefer xenbus_write() over xenbus_printf() where possible
Date: Thu, 7 Jul 2016 12:12:24 +0100 [thread overview]
Message-ID: <577E3918.5030303@citrix.com> (raw)
In-Reply-To: <577E282002000078000FBECB@prv-mh.provo.novell.com>
On 07/07/16 09:00, Jan Beulich wrote:
> ... as being the simpler variant.
It's really annoying that all these related cleanups where not in the
same thread. Don't do this again, please.
The better clean-up is to remove xenbus_write() in favour of
xenbus_printf() everywhere (especially since one of your "cleanups" made
it worse).
xenbus_printf() does everything xenbus_write() can do with no loss of
readability.
David
next prev parent reply other threads:[~2016-07-07 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 8:00 [PATCH] xen-netfront: prefer xenbus_write() over xenbus_printf() where possible Jan Beulich
2016-07-07 8:00 ` Jan Beulich
2016-07-07 11:12 ` David Vrabel
2016-07-07 11:12 ` David Vrabel [this message]
2016-07-07 12:05 ` Jan Beulich
2016-07-07 12:05 ` [Xen-devel] " Jan Beulich
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=577E3918.5030303@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.