From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, axboe@suse.de, greg@kroah.com
Subject: Re: [GIT PATCH] SCSI merge for 2.6.13
Date: Wed, 7 Sep 2005 17:59:06 -0700 [thread overview]
Message-ID: <20050907175906.09b0a46f.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0509071743380.11102@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
>
>
>
> On Wed, 7 Sep 2005, Linus Torvalds wrote:
> >
> > Quite frankly, what's the point in asking people to pull a tree that is
> > known to not compile?
James was assuming you'd merged the klist patch whcih I'd sent beforehand.
> Btw, I see the patch that is supposed to fix it, but I'm in no position to
> know whether it's even acceptable to basically double the size of the
> "struct klist", for example. There may be a good reason why Greg hasn't
> been merging the klist stuff,
This patch came out around the time Greg went walkabout.
I'd suggest we merge the klist patch anyway, so it doesn't hold up scsi.
If Greg wants to fix that bug by other means later on, we can do that
anytime.
next prev parent reply other threads:[~2005-09-08 1:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 0:37 [GIT PATCH] SCSI merge for 2.6.13 James Bottomley
2005-09-07 17:47 ` Patrick Mansfield
2005-09-07 18:14 ` James Bottomley
2005-09-07 19:35 ` Jens Axboe
2005-09-08 0:31 ` Linus Torvalds
2005-09-08 0:40 ` James Bottomley
2005-09-08 0:41 ` Linus Torvalds
2005-09-08 0:49 ` Linus Torvalds
2005-09-08 0:56 ` James Bottomley
2005-09-08 0:59 ` Andrew Morton [this message]
2005-09-08 0:53 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 2:44 [GIT PATCH] scsi " 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=20050907175906.09b0a46f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@SteelEye.com \
--cc=axboe@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.org \
/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