From: Greg KH <greg@kroah.com>
To: Timur Tabi <timur@freescale.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linuxppc-dev@lists.ozlabs.org, alan@lxorguk.ukuu.org.uk,
kumar.gala@freescale.com, benh@kernel.crashing.org,
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 13:31:17 -0700 [thread overview]
Message-ID: <20110609203117.GB14235@kroah.com> (raw)
In-Reply-To: <4DF12A94.6070605@freescale.com>
On Thu, Jun 09, 2011 at 03:18:28PM -0500, 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?
Why is binary compatibility important? Isn't this a brand new driver
for a brand new system? What userspace tools are out there in the wild
for such a thing?
confused,
greg k-h
next prev parent reply other threads:[~2011-06-09 20:31 UTC|newest]
Thread overview: 12+ 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:40 ` Randy Dunlap
2011-06-09 19:47 ` Timur Tabi
2011-06-09 19:48 ` Randy Dunlap
2011-06-09 20:25 ` Arnd Bergmann
2011-06-09 20:13 ` Arnd Bergmann
2011-06-09 20:18 ` Timur Tabi
2011-06-09 20:31 ` Greg KH [this message]
2011-06-09 20:40 ` Timur Tabi
2011-06-09 20:33 ` Arnd Bergmann
2011-06-10 10:45 ` Mark Brown
2011-06-10 8:32 ` [PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisormanagement driver David Laight
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=20110609203117.GB14235@kroah.com \
--to=greg@kroah.com \
--cc=akpm@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox