From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jesper Juhl <jj@chaosbits.net>,
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, 08 Jan 2012 13:42:54 -0800 [thread overview]
Message-ID: <1326058974.5372.4.camel@joe2Laptop> (raw)
In-Reply-To: <CA+55aFwO9Wtq=NEpMskW-2wrWZAGh-C6VBXENA3LtFOk=tUwgQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-01-08 21:43 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 ` Joe Perches [this message]
2012-01-08 22:21 ` Please merge two small bug fix patches from linux-next Jesper Juhl
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=1326058974.5372.4.camel@joe2Laptop \
--to=joe@perches.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=jj@chaosbits.net \
--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®