From: Arnd Bergmann <arnd@arndb.de>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, alan@lxorguk.ukuu.org.uk,
kumar.gala@freescale.com, benh@kernel.crashing.org,
greg@kroah.com, akpm@kernel.org, cmetcalf@tilera.com,
konrad.wilk@oracle.com, linux-kernel@vger.kernel.org,
linux-console@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisor management driver
Date: Thu, 9 Jun 2011 22:33:07 +0200 [thread overview]
Message-ID: <201106092233.08030.arnd@arndb.de> (raw)
In-Reply-To: <4DF12A94.6070605@freescale.com>
On Thursday 09 June 2011 22:18:28 Timur Tabi wrote:
> > More importantly, the code you have chose (0) conflicts with existing drivers
> > (frame buffer, scsi and wavefront among others). Please chose a free one and
> > add it to Documentation/ioctl/ioctl-number.txt in the same patch.
>
> Ok, I was really hoping to avoid doing this. Like I said, binary compatibility
> is important, and changing the type will break my existing apps. Are you
> insisting that I pick a new number?
I definitely insist that you have a proper interface in the driver at the
time that it gets merged, and that probably includes a collision-free
ioctl code.
You can probably make the driver support both the traditional and the
new interface, but I would prefer if you kept that as a private patch
on top a clean kernel driver. It's also a good idea to keep the header
file clean and only define the new interface there, to ensure that all
applications that are built in the future have to use the new interface.
When you make the patch to add backwards compat support, just add it
to the driver itself, not to the header.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Timur Tabi <timur@freescale.com>
Cc: konrad.wilk@oracle.com, kumar.gala@freescale.com,
linux-kernel@vger.kernel.org, cmetcalf@tilera.com,
akpm@kernel.org, linux-console@vger.kernel.org, greg@kroah.com,
virtualization@lists.linux-foundation.org,
linuxppc-dev@lists.ozlabs.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisor management driver
Date: Thu, 9 Jun 2011 22:33:07 +0200 [thread overview]
Message-ID: <201106092233.08030.arnd@arndb.de> (raw)
In-Reply-To: <4DF12A94.6070605@freescale.com>
On Thursday 09 June 2011 22:18:28 Timur Tabi wrote:
> > More importantly, the code you have chose (0) conflicts with existing drivers
> > (frame buffer, scsi and wavefront among others). Please chose a free one and
> > add it to Documentation/ioctl/ioctl-number.txt in the same patch.
>
> Ok, I was really hoping to avoid doing this. Like I said, binary compatibility
> is important, and changing the type will break my existing apps. Are you
> insisting that I pick a new number?
I definitely insist that you have a proper interface in the driver at the
time that it gets merged, and that probably includes a collision-free
ioctl code.
You can probably make the driver support both the traditional and the
new interface, but I would prefer if you kept that as a private patch
on top a clean kernel driver. It's also a good idea to keep the header
file clean and only define the new interface there, to ensure that all
applications that are built in the future have to use the new interface.
When you make the patch to add backwards compat support, just add it
to the driver itself, not to the header.
Arnd
next prev parent reply other threads:[~2011-06-09 20:33 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 19:13 [PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisor management driver Timur Tabi
2011-06-09 19:13 ` Timur Tabi
2011-06-09 19:40 ` Randy Dunlap
2011-06-09 19:40 ` Randy Dunlap
2011-06-09 19:40 ` Randy Dunlap
2011-06-09 19:40 ` Randy Dunlap
2011-06-09 19:47 ` Timur Tabi
2011-06-09 19:47 ` Timur Tabi
2011-06-09 19:47 ` Timur Tabi
2011-06-09 19:47 ` Timur Tabi
2011-06-09 19:48 ` Randy Dunlap
2011-06-09 19:48 ` Randy Dunlap
2011-06-09 19:48 ` Randy Dunlap
2011-06-09 20:25 ` Arnd Bergmann
2011-06-09 20:25 ` Arnd Bergmann
2011-06-09 20:25 ` Arnd Bergmann
2011-06-09 20:13 ` Arnd Bergmann
2011-06-09 20:13 ` Arnd Bergmann
2011-06-09 20:13 ` Arnd Bergmann
2011-06-09 20:18 ` Timur Tabi
2011-06-09 20:18 ` Timur Tabi
2011-06-09 20:18 ` Timur Tabi
2011-06-09 20:18 ` Timur Tabi
2011-06-09 20:31 ` Greg KH
2011-06-09 20:31 ` Greg KH
2011-06-09 20:40 ` Timur Tabi
2011-06-09 20:40 ` Timur Tabi
2011-06-09 20:40 ` Timur Tabi
2011-06-09 20:40 ` Timur Tabi
2011-06-09 20:31 ` Greg KH
2011-06-09 20:33 ` Arnd Bergmann [this message]
2011-06-09 20:33 ` Arnd Bergmann
2011-06-10 10:45 ` Mark Brown
2011-06-10 10:45 ` Mark Brown
2011-06-10 10:45 ` Mark Brown
2011-06-09 20:33 ` Arnd Bergmann
2011-06-10 8:32 ` [PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisormanagement driver David Laight
2011-06-10 8:32 ` David Laight
2011-06-10 8:32 ` David Laight
2011-06-10 8:32 ` David Laight
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 19:13 [PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisor management driver Timur Tabi
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=201106092233.08030.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.com \
--cc=greg@kroah.com \
--cc=konrad.wilk@oracle.com \
--cc=kumar.gala@freescale.com \
--cc=linux-console@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=timur@freescale.com \
--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 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.