LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
dougg@torque.net
Subject: Re: [GIT PATCH] final SCSI updates for 2.6.24 merge window
Date: Thu, 7 Feb 2008 19:24:58 -0800 [thread overview]
Message-ID: <20080207192458.77ea0778.akpm@linux-foundation.org> (raw)
In-Reply-To: <1202440603.3171.72.camel@localhost.localdomain>
On Thu, 07 Feb 2008 21:16:43 -0600 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Thu, 2008-02-07 at 18:46 -0800, Andrew Morton wrote:
> > On Thu, 07 Feb 2008 18:56:46 -0600 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> >
> > > Quite a bit of this is fixing things broken previously (the advansys fix
> > > is still pending resolution, but I'll send it as an -rc fix when we have
> > > it). There's the final elimination of all drivers that are esp based
> > > but don't use the scsi_esp core (that's mostly m68k and alpha). Plus
> > > the usual bunch of driver updates and the addition of a new enclosure
> > > services driver and the corresponding ULD.
> >
> > Sob. Can we please merge "Convert SG from nopage to fault"? It has been
> > sent three times, the first time was Dec 5 last year and it has thus far
> > received the lead balloon treatment. Despite my explicit request for
> > consideration last time I sent it
> >
> > If there is no movement here then I have to carry the moderately intrusive
> > mm-remove-nopage.patch for another N months and we need to watch out for
> > new ->nopage implementations popping up etc.
>
> I agree ... I've pinged Doug privately, this is publicly.
> Unfortunately, it is an intrusive change and needs testing .. I just
> don't have the tools that do this for SG.
>
I keep on forgetting that sg==dougg.
<looks in MAINTAINERS. Shifts blame.>
In fact scsi is the area in which I have the most who-maintains-what
trouble. I just don't believe what MAINTAINERS says about scsi drivers and
I tend to resort to git-whatchanged to find out who's really doing stuff.
The number of people@lsil.com makes my head spin and I tend to cc as many
as I can get my hands on.
IOW: some care and attention to the ./MAINTAINERS file would really help
here.
prev parent reply other threads:[~2008-02-08 3:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 0:56 James Bottomley
2008-02-08 1:04 ` Harvey Harrison
2008-02-08 1:07 ` James Bottomley
2008-02-08 1:14 ` Harvey Harrison
2008-02-08 9:03 ` Geert Uytterhoeven
2008-02-08 16:37 ` James Bottomley
2008-02-11 21:13 ` Harvey Harrison
2008-02-11 22:02 ` James Bottomley
2008-02-08 1:37 ` James Bottomley
2008-02-08 3:53 ` FUJITA Tomonori
2008-02-08 2:46 ` Andrew Morton
2008-02-08 3:11 ` Linus Torvalds
2008-02-08 5:05 ` Christoph Hellwig
2008-02-08 3:16 ` James Bottomley
2008-02-08 3:24 ` Andrew Morton [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=20080207192458.77ea0778.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=torvalds@linux-foundation.org \
--subject='Re: [GIT PATCH] final SCSI updates for 2.6.24 merge window' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).