From: Paul Bolle <pebolle@tiscali.nl>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, b.reynal@virtualopensystems.com,
linux-kernel@vger.kernel.org, eric.auger@linaro.org
Subject: Re: [PATCH] vfio: Split virqfd into a separate module for vfio bus drivers
Date: Thu, 19 Mar 2015 21:31:51 +0100 [thread overview]
Message-ID: <1426797111.23529.29.camel@x220> (raw)
In-Reply-To: <1426795931.3643.455.camel@redhat.com>
On Thu, 2015-03-19 at 14:12 -0600, Alex Williamson wrote:
> Well, at some point when I was doing vfio it seemed like a good idea and
> I copied it from another driver.
For some time now I have this idea that there's a Linux kernel module
template somewhere that uses defines like the ones you're using. That
all started when I noticed drivers defining DRIVER_LICENSE. (I really
like the name of that define.) Because every driver defining it ends up
using it only once.
> Is it more valuable to remove a few lines of source code with no net
> effect on the resulting output?
We should discuss this from the opposite direction: why is this patch
adding a few lines with no obvious benefit?
> Besides, look at how much more aesthetically pleasing the above is
> versus this:
>
> MODULE_VERSION("0.1");
> MODULE_LICENSE("GPL v2");
> MODULE_AUTHOR("Alex Williamson <alex.williamson@redhat.com>");
> MODULE_DESCRIPTION("IRQFD support for VFIO bus drivers");
>
> ;)
I don't do smileys. Perhaps that's why I never know what to think when
someone uses them. Anyhow, sure, my comment is extremely trivial, but I
do think I should raise this point just once. Because, well, ...
because!
Paul Bolle
prev parent reply other threads:[~2015-03-19 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 17:27 [PATCH] vfio: Split virqfd into a separate module for vfio bus drivers Alex Williamson
2015-03-19 19:32 ` Paul Bolle
2015-03-19 20:12 ` Alex Williamson
2015-03-19 20:31 ` Paul Bolle [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=1426797111.23529.29.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=alex.williamson@redhat.com \
--cc=b.reynal@virtualopensystems.com \
--cc=eric.auger@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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