From: Tom Duffy <tduffy@sun.com>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: Olaf Hering <olh@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi@vger.kernel.org
Subject: RE: [PATCH 22/82] remove linux/version.h from drivers/message/fus ion
Date: Tue, 12 Jul 2005 13:30:20 -0700 [thread overview]
Message-ID: <1121200220.13708.17.camel@duffman> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C030A908F@nacos172.co.lsil.com>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Sun, 2005-07-10 at 18:15 -0600, Moore, Eric Dean wrote:
> I'd rather you not kill linux_compat.h file.
> I use this file for compatibility of driver source
> across various kernel versions. I provide our
> customers with driver builds containing single source
> which needs to compile in kernels 2.6.5( e.g. SLES9),
> 2.6.8 (e.g. RHEL4), and 2.6.11 ( e.g. SuSE 9.3 Pro).
It is the general policy that the source in the latest linux kernel only
supports that kernel. You can certainly keep a compat header for your
customers, but what is in kernel.org should be clean for that version of
the kernel.
> If you look at our 3.02.18 driver source I submitted to SuSE
> for SLES9 SP2, you will see this file is about 3K bytes of
> compatibility.
Is the 3.02.18 code generally available now? Can it be cleaned up for
submission to 2.6.13?
-tduffy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-12 20:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 0:15 [PATCH 22/82] remove linux/version.h from drivers/message/fus ion Moore, Eric Dean
2005-07-12 20:30 ` Tom Duffy [this message]
2005-07-13 2:16 ` Matt Domsch
2005-07-13 14:37 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 20:50 Moore, Eric Dean
2005-07-12 20:56 ` Tom Duffy
2005-07-12 22:14 ` David S. Miller
2005-07-12 22:34 Moore, Eric Dean
2005-07-13 15:11 Moore, Eric Dean
2005-07-20 0:07 Moore, Eric Dean
2005-07-20 3:12 ` Matt Domsch
2005-07-20 4:28 ` Stephen Rothwell
2005-07-20 5:09 ` Moore, Eric Moore
2005-07-20 8:30 ` Bernd Petrovitsch
2005-07-20 12:48 ` Matthew Wilcox
2005-07-20 17:54 ` Nathan Lynch
2005-07-20 18:22 ` Matt Domsch
2005-07-20 17:55 ` Nish Aravamudan
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=1121200220.13708.17.camel@duffman \
--to=tduffy@sun.com \
--cc=Eric.Moore@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=olh@suse.de \
/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