From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <greg@kroah.com>
Cc: linux-scsi@vger.kernel.org, Tony Jones <tonyj@suse.de>,
Kay Sievers <kay.sievers@vrfy.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org
Subject: Re: [patch] convert the scsi layer to use struct device
Date: Mon, 17 Mar 2008 12:57:20 -0500 [thread overview]
Message-ID: <1205776640.6767.154.camel@localhost.localdomain> (raw)
In-Reply-To: <1205514958.2904.27.camel@localhost.localdomain>
On Fri, 2008-03-14 at 12:15 -0500, James Bottomley wrote:
> On Thu, 2008-03-13 at 14:06 -0700, Greg KH wrote:
> > Here's a huge patch from Tony and Kay that converts the scsi layer to
> > use struct device instead of class_device.
> >
> > It doesn't seem like it could be split up any smaller due to the
> > interconectedness of the whole mess, if you have any suggestions
> > otherwise, it would be appreciated.
> >
> > If you want, I can take this through my tree as it does depend on a
> > previous IB patch to make that portion of the patch much smaller.
> >
> > After this, all of the class_device code is now finally gone from the
> > kernel!
>
> Actually, I have it built and running (actually 2.6.25-rc5-mc5 which
> includes all the changes in your tree). Amazingly it's pretty much
> fully functional, except ses which seems to have suffered a breakdown in
> the way its model works. I'll see if I can fix it up.
>
> Since the patch is separable, it's probably best to take it through the
> SCSI tree ... including the infiniband bits that depend on the
> iser/iscsi transport classes. You can give the rest of the infiniband
> pieces to roland, since he's got a nasty set of clashes with the
> __FUNCTION__->__func__ conversion which I don't want to be responsible
> for.
OK, I've changed my mind ... it doesn't really work well without all the
rest of the pieces ... plus I think there are going to be merge nasties
which I'd rather you sorted out.
What I'll do is run a scsi-post-merge-2.6 tree here:
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-post-merge-2.6.git;a=summary
I've dropped a quasi stable branch from your quilt tree and plumbed it
into the -mc tree generation machinery, so it will warn me if you make
too radical an alteration to your quilt.
Andrew,
you probably won't be able to pull this into -mm without the -mc
machinery, so the best thing will simply to be to pull in the changes
patch here right at the end of the -mm build (the same goes for
linux-next):
http://www.kernel.org/pub/linux/kernel/people/jejb/scsi-post-merge-2.6.diff
It's a roll up patch of only the SCSI pieces. It's updated every time I
push a patch, so it should always be current.
James
next prev parent reply other threads:[~2008-03-17 17:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 21:06 [patch] convert the scsi layer to use struct device Greg KH
2008-03-14 14:13 ` Hannes Reinecke
2008-03-14 17:15 ` James Bottomley
2008-03-14 21:20 ` James Bottomley
2008-03-14 21:58 ` Kay Sievers
2008-03-15 14:19 ` James Bottomley
2008-03-15 15:17 ` Kay Sievers
2008-03-15 16:16 ` James Bottomley
2008-03-15 18:01 ` James Bottomley
2008-03-15 18:26 ` Kay Sievers
2008-03-15 18:34 ` James Bottomley
2008-03-15 20:38 ` Stefan Richter
2008-03-15 18:04 ` Kay Sievers
2008-03-15 18:31 ` James Bottomley
2008-03-15 18:56 ` Kay Sievers
2008-03-15 19:33 ` James Bottomley
2008-03-15 19:43 ` Kay Sievers
2008-03-16 20:21 ` James Smart
2008-03-16 21:04 ` Kay Sievers
2008-03-17 4:15 ` James Smart
2008-03-17 5:35 ` Greg KH
2008-03-17 12:18 ` James Smart
2008-03-17 13:40 ` Kay Sievers
2008-03-17 13:55 ` James Bottomley
2008-03-17 17:57 ` James Bottomley [this message]
2008-03-19 0:48 ` Greg KH
2008-03-19 20:38 ` James Bottomley
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=1205776640.6767.154.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tonyj@suse.de \
/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.