From: Jesper Juhl <jj@chaosbits.net>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Al Viro <viro@zeniv.linux.org.uk>, Eric Paris <eparis@redhat.com>
Subject: Re: Please merge two small bug fix patches from linux-next
Date: Sun, 8 Jan 2012 23:21:39 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1201082319560.24030@swampdragon.chaosbits.net> (raw)
In-Reply-To: <1326058974.5372.4.camel@joe2Laptop>
On Sun, 8 Jan 2012, Joe Perches wrote:
> On Sun, 2012-01-08 at 13:26 -0800, Linus Torvalds wrote:
> > On Sun, Jan 8, 2012 at 11:51 AM, Jesper Juhl <jj@chaosbits.net> wrote:
> > > Below are two patches that have been in linux-next for ages (via akpm's
> > > tree). They are prette simple, straight-up, bug fixes. They have been
> > > submitted to maintainers multiple times over (IIRC at least the past
> > > year), but for some reason the maintainers seem uninterested in picking
> > > them up (or even responding to them).
> []
> > they seem to have Andrew's sign-off, so I'd have expected them to
> > come through Andew. What's up?
>
> >From my perspective, the issue lies with James'
> apparent desire to keep scsi tree changes as close
> to zero as possible.
>
> Many obvious corrections to scsi defects have gone
> unapplied.
>
I have to agree. It's actually gotten to the point that I personally
completely avoid/ignore scsi code when looking for stuff to fix/improve
since I don't expect to be able to get the patches merged anyway..
--
Jesper Juhl <jj@chaosbits.net> http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.
next prev parent reply other threads:[~2012-01-08 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 19:51 Jesper Juhl
2012-01-08 21:26 ` Linus Torvalds
2012-01-08 21:35 ` Jesper Juhl
2012-01-08 21:44 ` [PATCH] drivers/scsi/aacraid/commctrl.c: fix mem leak in aac_send_raw_srb() Jesper Juhl
2012-01-08 21:44 ` [PATCH] audit: always follow va_copy() with va_end() Jesper Juhl
2012-01-08 21:42 ` Please merge two small bug fix patches from linux-next Joe Perches
2012-01-08 22:21 ` Jesper Juhl [this message]
2012-01-08 23:14 ` Harvey Harrison
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=alpine.LNX.2.00.1201082319560.24030@swampdragon.chaosbits.net \
--to=jj@chaosbits.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®