From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] SCSI bug fixes for 2.6.25-rc1
Date: Wed, 13 Feb 2008 20:10:53 -0600 [thread overview]
Message-ID: <1202955053.3109.104.camel@localhost.localdomain> (raw)
In-Reply-To: <20080213.172251.249294145.davem@davemloft.net>
On Wed, 2008-02-13 at 17:22 -0800, David Miller wrote:
> From: James Bottomley <James.Bottomley@HansenPartnership.com>
> Date: Wed, 13 Feb 2008 19:11:53 -0600
>
> >
> > On Wed, 2008-02-13 at 16:16 -0800, Andrew Morton wrote:
> > > kill-warnings-in-mptbaseh-on-parisc64.patch
> >
> > > Warning fixes.
> >
> > Not sure ... LSI is supposed to be processing this.
>
> James, please don't push build warning fixes and the like back to the
> driver maintainers.
>
> This is your domain as SCSI maintainer, and you should integrate these
> kinds of things directly and as promptly as possible.
>
> This is doubly true if the "driver maintainer" can't be bothered
> to ACK or fixup the patch for months.
>
> Otherwise this kind of stuff rots, and diligent people like Andrew
> (and the patch submitter, whoever that might be) get extremely
> frustrated.
LSI did ask to merge through their patch process, but I agree this one's
been hanging around for a bit long.
James
next prev parent reply other threads:[~2008-02-14 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 0:02 [GIT PATCH] SCSI bug fixes for 2.6.25-rc1 James Bottomley
2008-02-14 0:16 ` Andrew Morton
2008-02-14 1:11 ` James Bottomley
2008-02-14 1:22 ` David Miller
2008-02-14 2:10 ` James Bottomley [this message]
2008-02-14 3:34 ` Andrew Morton
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=1202955053.3109.104.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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