From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <greg@kroah.com>
Cc: linux-parisc@vger.kernel.org, Kyle McMartin <kyle@mcmartin.ca>,
Matthew Wilcox <matthew@wil.cx>,
Grant Grundler <grundler@parisc-linux.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH] parisc: don't touch driver core internals
Date: Wed, 28 Jan 2009 11:25:19 -0600 [thread overview]
Message-ID: <1233163519.3236.82.camel@localhost.localdomain> (raw)
In-Reply-To: <20090127010733.GA21660@kroah.com>
On Mon, 2009-01-26 at 17:07 -0800, Greg KH wrote:
> From: Greg Kroah-Hartman <gregkh@suse.de>
>
> It isn't wise to use the struct device klists on their own, as their
> implementation has a tendancy to change at times. Instead, use the
> functions created for iterating over lists of devices, as it handles all
> of the dirty klist work for you automatically.
>
> This is needed as the driver core is changing how klists are stored in
> struct device in the near future.
>
> Cc: Kyle McMartin <kyle@mcmartin.ca>
> Cc: Matthew Wilcox <matthew@wil.cx>
> Cc: Grant Grundler <grundler@parisc-linux.org>
> Cc: Kay Sievers <kay.sievers@vrfy.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> ---
>
> I can keep this in my driver-core tree, where is it required in order
> for parisc to build properly. Or you all can take this now, in your
> tree, whatever is easier for you.
>
> drivers/char/agp/parisc-agp.c | 24 ++++++---------
> drivers/parisc/gsc.c | 40 +++++++++++++++-----------
> drivers/parisc/sba_iommu.c | 64 ++++++++++++++++++++++++------------------
> 3 files changed, 71 insertions(+), 57 deletions(-)
Actually, we already have such a patch here:
http://marc.info/?l=linux-parisc&m=123154903507114
The approaches look identical.
James
next prev parent reply other threads:[~2009-01-28 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 1:07 [PATCH] parisc: don't touch driver core internals Greg KH
2009-01-28 17:25 ` James Bottomley [this message]
2009-01-28 17:35 ` Greg KH
2009-01-28 17:41 ` Kyle McMartin
2009-01-28 17:58 ` Greg KH
2009-01-30 15:10 ` Kyle McMartin
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=1233163519.3236.82.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=kay.sievers@vrfy.org \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
/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