mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mark Asselstine" <asselsm@gmail.com>
To: "Alexander Beregalov" <a.beregalov@gmail.com>
Cc: "Ian Romanick" <ianr@q7.com>,
	airlied@linux.ie, dri-devel@lists.sourceforge.net,
	kernel-janitors@vger.kernel.org,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm_memory.h: remove double inclusion of linux/vmalloc.h
Date: Tue, 8 Jul 2008 20:28:07 -0400	[thread overview]
Message-ID: <919fe2b30807081728n1ce1d0eckf1172386c22a0cf7@mail.gmail.com> (raw)
In-Reply-To: <a4423d670807080956m4aa548b7vf5557892aae81432@mail.gmail.com>

On Tue, Jul 8, 2008 at 12:56 PM, Alexander Beregalov
<a.beregalov@gmail.com> wrote:
> 2008/7/8 Ian Romanick <ianr@q7.com>:
>> On Tue, Jul 08, 2008 at 08:29:57AM -0400, Mark Asselstine wrote:
>>> On Sun, Jul 6, 2008 at 7:31 AM, Alexander Beregalov
>>> <a.beregalov@gmail.com> wrote:
>>> > From: Alexander Beregalov <a.beregalov@gmail.com>
>>> >
>>> >  #if __OS_HAS_AGP
>>> >
>>> > -#include <linux/vmalloc.h>
>>> > -
>>>
>>> Why remove this one and not the one at the top of the file? As well
>>
>> I would assume this one is removed because it is inside additional
>> ifdefs.
> Yes, it does not change functionality of the code.

I guess I even question if this include should actually be anywhere in
this file.

>>
>>> this file has #include of drmP.h, yet drmP.h is the only file I can
>>> find that includes drm_memory.h. Based on this I would think there is
>>> some additional cleanup that can go on here.
> How it can be cleaned up? Do you mean to move `define PAGE_AGP` to drmP.h?
>

It looks to me like this file at one time was meant to be included by
files other then drmP.h. Including drmP.h ensured __OS_HAS_AGP was
defined and a circular dependence was prevented by ifdefs surrounding
the bulk of drmP.h. As far as I can tell none of the includes in this
file are necessary anymore and a quick x86 compile seems to back me up
(please double check however). Once these are removed there is very
little functionality left and it might make more sense to just put in
into drmP.h. If in the future there is a need for this type of include
it can be started from scratch but for now I would say it should go
away.

Regards,
Mark

      reply	other threads:[~2008-07-09  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06 11:31 Alexander Beregalov
2008-07-08 12:29 ` Mark Asselstine
2008-07-08 15:22   ` Ian Romanick
2008-07-08 16:56     ` Alexander Beregalov
2008-07-09  0:28       ` Mark Asselstine [this message]

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=919fe2b30807081728n1ce1d0eckf1172386c22a0cf7@mail.gmail.com \
    --to=asselsm@gmail.com \
    --cc=a.beregalov@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=ianr@q7.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®