From: Timur Tabi <timur@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, 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-console@vger.kernel.org
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Thu, 9 Jun 2011 15:24:27 -0500 [thread overview]
Message-ID: <4DF12BFB.5030102@freescale.com> (raw)
In-Reply-To: <201106092220.22246.arnd@arndb.de>
Arnd Bergmann wrote:
> The lesson to learn here is obviously not to ship binaries of applications
> to customers before the driver has been merged in a mainline kernel.
Believe me, I know this, but unfortunately I have no control over every aspect
of our development cycle.
> The best way out that I can see is to make the driver carry the proper
> interface in the upstream version, but to have a private patch to support
> both interface versions in the kernel you ship on machines that require
> backwards compatibility. Once you have phased out the user application,
> you can then drop that patch and use the upstream version of the
> interfaces.
I think I can make that work.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
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,
linuxppc-dev@lists.ozlabs.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Thu, 9 Jun 2011 15:24:27 -0500 [thread overview]
Message-ID: <4DF12BFB.5030102@freescale.com> (raw)
In-Reply-To: <201106092220.22246.arnd@arndb.de>
Arnd Bergmann wrote:
> The lesson to learn here is obviously not to ship binaries of applications
> to customers before the driver has been merged in a mainline kernel.
Believe me, I know this, but unfortunately I have no control over every aspect
of our development cycle.
> The best way out that I can see is to make the driver carry the proper
> interface in the upstream version, but to have a private patch to support
> both interface versions in the kernel you ship on machines that require
> backwards compatibility. Once you have phased out the user application,
> you can then drop that patch and use the upstream version of the
> interfaces.
I think I can make that work.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <linux-kernel@vger.kernel.org>, <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-console@vger.kernel.org>
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Thu, 9 Jun 2011 15:24:27 -0500 [thread overview]
Message-ID: <4DF12BFB.5030102@freescale.com> (raw)
In-Reply-To: <201106092220.22246.arnd@arndb.de>
Arnd Bergmann wrote:
> The lesson to learn here is obviously not to ship binaries of applications
> to customers before the driver has been merged in a mainline kernel.
Believe me, I know this, but unfortunately I have no control over every aspect
of our development cycle.
> The best way out that I can see is to make the driver carry the proper
> interface in the upstream version, but to have a private patch to support
> both interface versions in the kernel you ship on machines that require
> backwards compatibility. Once you have phased out the user application,
> you can then drop that patch and use the upstream version of the
> interfaces.
I think I can make that work.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-06-09 20:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 22:45 [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver Timur Tabi
2011-06-08 22:45 ` Timur Tabi
2011-06-08 23:10 ` Randy Dunlap
2011-06-08 23:10 ` Randy Dunlap
2011-06-08 23:10 ` Randy Dunlap
2011-06-08 23:16 ` Timur Tabi
2011-06-08 23:16 ` Timur Tabi
2011-06-08 23:16 ` Timur Tabi
2011-06-09 7:38 ` Arnd Bergmann
2011-06-09 7:38 ` Arnd Bergmann
2011-06-09 7:38 ` Arnd Bergmann
2011-06-09 16:32 ` Randy Dunlap
2011-06-09 16:32 ` Randy Dunlap
2011-06-09 16:32 ` Randy Dunlap
2011-06-09 16:36 ` Timur Tabi
2011-06-09 16:36 ` Timur Tabi
2011-06-09 16:36 ` Timur Tabi
2011-06-09 16:42 ` Randy Dunlap
2011-06-09 16:42 ` Randy Dunlap
2011-06-09 16:42 ` Randy Dunlap
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:36 ` Timur Tabi
2011-06-10 14:17 ` Chris Metcalf
2011-06-10 14:17 ` Chris Metcalf
2011-06-10 14:17 ` Chris Metcalf
2011-06-10 14:17 ` Chris Metcalf
2011-06-10 15:36 ` Arnd Bergmann
2011-06-10 15:36 ` Arnd Bergmann
2011-06-10 15:36 ` Arnd Bergmann
2011-06-09 7:29 ` Arnd Bergmann
2011-06-09 7:29 ` Arnd Bergmann
2011-06-09 18:55 ` Timur Tabi
2011-06-09 18:55 ` Timur Tabi
2011-06-09 18:55 ` Timur Tabi
2011-06-09 20:20 ` Arnd Bergmann
2011-06-09 20:20 ` Arnd Bergmann
2011-06-09 20:24 ` Timur Tabi [this message]
2011-06-09 20:24 ` Timur Tabi
2011-06-09 20:24 ` 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=4DF12BFB.5030102@freescale.com \
--to=timur@freescale.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=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 \
/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.