From: jbarnes@sgi.com (Jesse Barnes)
To: Greg KH <greg@kroah.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, jeremy@sgi.com
Subject: Re: [PATCH] readX_relaxed interface
Date: Fri, 16 Jan 2004 02:21:55 +0000 [thread overview]
Message-ID: <20040116022155.GA10634@sgi.com> (raw)
In-Reply-To: <20040116003224.GF23253@kroah.com>
On Thu, Jan 15, 2004 at 04:32:25PM -0800, Greg KH wrote:
> It looks ok, but it would really be good if we could indicate if the
> read actually was successful. Right now some platforms can detect
> faults and do not have a way to get that error back to the driver in a
> sane manner. If we were to change the read* functions to look something
> like:
> int readb(void *addr, u8 *data);
> it would be a world easier.
At one point, I thought it would be nice if it took a struct device *
too, but that's probably a bit much.
> Now I'm not saying I want to change the existing interfaces to support
> this, that's too much code to change for even me (and is a 2.7 thing.)
>
> Just wanted to put this idea in people's heads that we need to start
> planning for something like it.
Sounds reasonable. It should be helpful.
Thanks,
Jesse
WARNING: multiple messages have this Message-ID (diff)
From: jbarnes@sgi.com (Jesse Barnes)
To: Greg KH <greg@kroah.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, jeremy@sgi.com
Subject: Re: [PATCH] readX_relaxed interface
Date: Thu, 15 Jan 2004 18:21:55 -0800 [thread overview]
Message-ID: <20040116022155.GA10634@sgi.com> (raw)
In-Reply-To: <20040116003224.GF23253@kroah.com>
On Thu, Jan 15, 2004 at 04:32:25PM -0800, Greg KH wrote:
> It looks ok, but it would really be good if we could indicate if the
> read actually was successful. Right now some platforms can detect
> faults and do not have a way to get that error back to the driver in a
> sane manner. If we were to change the read* functions to look something
> like:
> int readb(void *addr, u8 *data);
> it would be a world easier.
At one point, I thought it would be nice if it took a struct device *
too, but that's probably a bit much.
> Now I'm not saying I want to change the existing interfaces to support
> this, that's too much code to change for even me (and is a 2.7 thing.)
>
> Just wanted to put this idea in people's heads that we need to start
> planning for something like it.
Sounds reasonable. It should be helpful.
Thanks,
Jesse
next prev parent reply other threads:[~2004-01-16 2:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 20:49 [PATCH] readX_relaxed interface Jesse Barnes
2004-01-15 20:49 ` Jesse Barnes
2004-01-15 22:16 ` Grant Grundler
2004-01-15 22:16 ` Grant Grundler
2004-01-15 22:56 ` Jesse Barnes
2004-01-15 22:56 ` Jesse Barnes
2004-01-16 3:19 ` Jeremy Higdon
2004-01-16 3:19 ` Jeremy Higdon
2004-01-16 0:32 ` Greg KH
2004-01-16 0:32 ` Greg KH
2004-01-16 2:21 ` Jesse Barnes [this message]
2004-01-16 2:21 ` Jesse Barnes
2004-01-16 5:00 ` Linus Torvalds
2004-01-16 5:00 ` Linus Torvalds
2004-01-16 17:21 ` Jesse Barnes
2004-01-16 17:21 ` Jesse Barnes
2004-01-16 5:00 ` Grant Grundler
2004-01-16 5:00 ` Grant Grundler
2004-01-19 9:31 ` Hironobu Ishii
2004-01-19 9:31 ` Hironobu Ishii
2004-01-19 18:18 ` Grant Grundler
2004-01-19 18:18 ` Grant Grundler
2004-01-16 5:50 ` Grant Grundler
2004-01-16 5:50 ` Grant Grundler
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=20040116022155.GA10634@sgi.com \
--to=jbarnes@sgi.com \
--cc=greg@kroah.com \
--cc=jeremy@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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.