xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] xen: remove DEFINE_XENBUS_DRIVER() macro
Date: Tue, 9 Sep 2014 10:53:57 +0100	[thread overview]
Message-ID: <540ECE35.10503@citrix.com> (raw)
In-Reply-To: <540EE58D020000780003275B@mail.emea.novell.com>

On 09/09/14 10:33, Jan Beulich wrote:
>>>> On 08.09.14 at 18:46, <david.vrabel@citrix.com> wrote:
>> The DEFINE_XENBUS_DRIVER() macro looks a bit weird and causes sparse
>> errors.
>>
>> Replace the uses with standard structure definitions instead.  This is
>> similar to pci and usb device registration.
>>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> 
> I really regret you doing this, re-adding redundancy the elimination
> of which the macro got added for (the diffstat would look even less
> favorable if your patch didn't eliminate a couple of bogus comments
> and blank lines). I'm certainly not in the position to nack this patch,
> but if I was I would.

There didn't seem to be a good reason to require that the driver name
match the first device ID.  What should the driver be named if it was
for two or more different types of Xenbus device? And not all drivers
did this anyway.

However, we could do:

  drv->driver.name = drv->name ? drv->name : drv->ids[0];

What that resolve your concern?

David

  reply	other threads:[~2014-09-09  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 16:46 [PATCH] xen: remove DEFINE_XENBUS_DRIVER() macro David Vrabel
2014-09-09  9:33 ` Jan Beulich
2014-09-09  9:53   ` David Vrabel [this message]
2014-09-09 10:15     ` 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=540ECE35.10503@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --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).