From: Jeff Garzik <jeff@garzik.org>
To: "Moore, Eric" <Eric.Moore@lsil.com>
Cc: akpm@osdl.org, James.Bottomley@steeleye.com,
linux-scsi@vger.kernel.org, michal.k.k.piotrowski@gmail.com
Subject: Re: [patch 20/28] drivers/message/fusion/linux_compat.h Removal of old code
Date: Mon, 25 Sep 2006 20:22:32 -0400 [thread overview]
Message-ID: <451872C8.7000400@garzik.org> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D7034FA42@NAMAIL4.ad.lsil.com>
Moore, Eric wrote:
> However pls don't remove this file from the tree.
Why? That's against the general kernel policy...
As an example, when maintaining libata for 2.4 kernels as well as 2.6
kernels, I had a libata-compat.h file, and always just patched the
include into the kernel source at the same time I patched in the
libata-compat.h contents.
Jeff
next prev parent reply other threads:[~2006-09-26 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 0:14 [patch 20/28] drivers/message/fusion/linux_compat.h Removal of old code Moore, Eric
2006-09-26 0:22 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-26 18:25 Moore, Eric
2006-09-26 18:30 ` Jeff Garzik
2006-09-25 23:59 akpm
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=451872C8.7000400@garzik.org \
--to=jeff@garzik.org \
--cc=Eric.Moore@lsil.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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.