From: Jesper Juhl <jj@chaosbits.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 22:35:13 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1201082228280.24030@swampdragon.chaosbits.net> (raw)
In-Reply-To: <CA+55aFwO9Wtq=NEpMskW-2wrWZAGh-C6VBXENA3LtFOk=tUwgQ@mail.gmail.com>
On Sun, 8 Jan 2012, 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).
> > There has been no negative comments at all to them while they have been in
> > -next.
> > I'd really appreciate it if they could get merged.
> >
> > I've just pulled them out of the current linux-next and applied them on
> > top of your tree - that's what is below.
>
> So where are they? Git tree or what?
>
> And if you want me to apply them as patches, please send them as
> proper individual patches instead of askng me to "merge" them.
>
> And they seem to have Andrew's sign-off, so I'd have expected them to
> come through Andew. What's up?
>
What's up is this: I'd submitted them a few times to the mailing list and
maintainers in the distant past. Andrew ended up picking them up when
maintainers didn't. Through him they made it into the linux-next tree and
have been living in Andrews queue and -next ever since.
I simply got fed up with seeing them in -next and getting nowhere, and
thought that if the maintainers won't pick them up maybe you would just
take them directly now since it's been ages and they have not gotten any
negative feedback and a merge window is open.
Andrew added his signed-off-by when he took them into his queue, I
retained that when I grabbed the patches into a mainline git clone from
-next, but I can just drop those if that's inappropriate.
I should not have said "merge" in the subject - my bad.
I'll send them as two individual patches by mail (unless you prefer a git
tree, then I can easily set that up as well).
--
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 21:35 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 [this message]
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
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.1201082228280.24030@swampdragon.chaosbits.net \
--to=jj@chaosbits.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.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®