From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Thibaut VARENE <T-Bone@parisc-linux.org>,
Antonino Daplas <adaplas@pol.net>,
Ben Dooks <ben-linux-arm@fluff.org>
Subject: Re: Re: [PATCH][RFC] Add support for Epson S1D13806 FB
Date: Mon, 14 Mar 2005 15:44:33 +0200 [thread overview]
Message-ID: <20050314134433.GC2695@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0503141425000.4784@numbat.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
On Mon, Mar 14, 2005 at 02:25:48PM +0100, Geert Uytterhoeven wrote:
> On Mon, 14 Mar 2005, Paul Mundt wrote:
> > While the pci_resource_xxx() routines would still technically do the
> > right thing, this is purely coincidental.
>
> Nah, they would work better here, since they do include the +1 ;-)
>
Indeed. However, using the pci_ prefixing here is a misnomer. It may be
worth having more generic struct resource accessors that take care of
this sort of thing, as clearly this is a common issue (perhaps
resource_start()/resource_len() or something equally silly).
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-03-14 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 10:13 [PATCH][RFC] Add support for Epson S1D13806 FB Thibaut VARENE
2005-03-14 12:15 ` Antonino A. Daplas
2005-03-14 13:00 ` Thibaut VARENE
2005-03-14 13:13 ` Antonino A. Daplas
2005-03-14 14:10 ` Antonino A. Daplas
2005-03-14 14:24 ` Thibaut VARENE
2005-03-14 15:06 ` Antonino A. Daplas
2005-03-14 14:35 ` Paul Mundt
2005-03-14 15:06 ` Antonino A. Daplas
2005-03-15 7:17 ` Paul Mundt
2005-03-15 10:26 ` Antonino A. Daplas
2005-03-14 15:18 ` Antonino A. Daplas
2005-03-14 13:18 ` Paul Mundt
2005-03-14 13:25 ` Geert Uytterhoeven
2005-03-14 13:34 ` Thibaut VARENE
2005-03-14 13:53 ` Antonino A. Daplas
2005-03-14 14:09 ` Thibaut VARENE
2005-03-14 14:12 ` Thibaut VARENE
2005-03-14 13:44 ` Paul Mundt [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=20050314134433.GC2695@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=T-Bone@parisc-linux.org \
--cc=adaplas@pol.net \
--cc=ben-linux-arm@fluff.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.