From: Kumar Gala <kumar.gala@freescale.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>,
"Gala Kumar K.-galak" <galak@freescale.com>,
<linux-kernel@vger.kernel.org>, "Andrew Morton" <akpm@osdl.org>,
<linux-ia64@vger.kernel.org>
Subject: Re: [PATCH 05/15] ia64: remove use of asm/segment.h
Date: Wed, 24 Aug 2005 16:32:59 -0500 [thread overview]
Message-ID: <95AE7798-CD53-4BEA-99F4-88FC5B475614@freescale.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F043851AD@scsmsx401.amr.corp.intel.com>
On Aug 24, 2005, at 3:19 PM, Luck, Tony wrote:
>> There are still a few drivers that include asm/segment.h, so
>> I don't think we should remove asm/segment.h itself just yet.
>>
>
> Agreed. The sequence should be to send patches to get rid of
> all "#include <asm/segment.h>" references.
>
> Once they have all gone, then a patch can remove the files.
>
> If you are concerned that people would start adding new
> references and you don't want to get into a game of whack-a-mole,
> then you could add #warning "include of deprecated asm/segment.h",
> but that might be overkill.
>
> I'll apply this for ia64 w/o the deletion.
I've posted a patch before this to remove all non-architecture users
of asm/segment.h.
http://www.ussg.iu.edu/hypermail/linux/kernel/0508.3/0099.html
- kumar
next prev parent reply other threads:[~2005-08-24 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 20:19 Luck, Tony
2005-08-24 21:32 ` Kumar Gala [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 21:42 Luck, Tony
2005-08-24 16:43 [PATCH 00/15] Remove asm/segment.h from low hanging architectures Kumar Gala
2005-08-24 16:53 ` [PATCH 05/15] ia64: remove use of asm/segment.h Kumar Gala
2005-08-24 20:09 ` Bjorn Helgaas
2005-08-24 22:49 ` Ralf Baechle
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=95AE7798-CD53-4BEA-99F4-88FC5B475614@freescale.com \
--to=kumar.gala@freescale.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=galak@freescale.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®