From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Why moving driver includes ?
Date: 28 Mar 2003 14:18:44 +0100 [thread overview]
Message-ID: <1048857524.12125.2.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0303280443170.11648-100000@phoenix.infradead.org>
Hi James !
Why did you move the driver includes to include/video ? What is
the reasoning here ?
For example, drivers/video/radeon.h moved to include/video/radeon.h
Is this to be able to share register definitions with the DRM drivers ?
(I doubt this will ever happen as the DRM is rather self contained)
I would have preferred those includes to stay next to their respective
drivers (though renaming radeon.h to radeonfb.h might have made some
sense).
Regards,
Ben.
next prev parent reply other threads:[~2003-03-28 13:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 19:57 Framebuffer fixes James Simmons
2003-03-27 3:01 ` [Linux-fbdev-devel] " Antonino Daplas
2003-03-27 9:09 ` Geert Uytterhoeven
2003-03-27 19:15 ` Antonino Daplas
2003-03-27 20:49 ` Geert Uytterhoeven
2003-03-27 20:49 ` Antonino Daplas
2003-03-28 4:48 ` James Simmons
2003-03-28 8:00 ` Geert Uytterhoeven
2003-03-28 11:02 ` Antonino Daplas
2003-03-28 13:18 ` Benjamin Herrenschmidt [this message]
2003-04-02 22:56 ` Why moving driver includes ? James Simmons
2003-03-27 20:43 ` [Linux-fbdev-devel] Framebuffer fixes Antonino Daplas
[not found] <mailman.1049324411.25620.linux-kernel2news@redhat.com>
2003-04-03 0:45 ` Why moving driver includes ? Pete Zaitcev
2003-04-03 1:32 ` Ulrich Drepper
2003-04-03 1:40 ` Pete Zaitcev
2003-04-04 13:30 ` Christoph Hellwig
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=1048857524.12125.2.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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®