From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: cluster-devel <cluster-devel@redhat.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
"Tobin C. Harding" <tobin@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] gfs2: Fix error path kobject memory leak
Date: Mon, 13 May 2019 15:47:22 -0700 [thread overview]
Message-ID: <CAHk-=wipiSQ=+dTssFhjYXUS0VgJYRNqy8s_YNTL8HbZ6iKsYg@mail.gmail.com> (raw)
In-Reply-To: <CAHc6FU43Fv_b9hMiRscs+cPbwLmcCBM-9R32fSsK9gUtMVMGUQ@mail.gmail.com>
On Mon, May 13, 2019 at 3:37 PM Andreas Gruenbacher <agruenba@redhat.com> wrote:
>
> Sorry, I should have been more explicit. Would you mind taking this
> patch, please? If it's more convenient or more appropriate, I'll send
> a pull request instead.
Done.
However,I'd like to point out that when I see patches from people who
I normally get a pull request from, I usually ignore them.
Particularly when they are in some thread with discussion, I'll often
just assume that th epatch is part of the thread, not really meant
for me in particular.
In this case I happened to notice that suddenly my participation
status changed, which is why I asked, but in general I might hav ejust
archived the thread with the assumption that I'll be getting the patch
later as a git pull.
Just so you'll be aware of this in the future, in case I don't react...
Linus
next prev parent reply other threads:[~2019-05-13 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 19:59 [PATCH] gfs2: Fix error path kobject memory leak Andreas Gruenbacher
2019-05-13 22:27 ` Linus Torvalds
2019-05-13 22:37 ` Andreas Gruenbacher
2019-05-13 22:47 ` Linus Torvalds [this message]
2019-05-13 22:57 ` Andreas Gruenbacher
-- strict thread matches above, loose matches on Subject: below --
2019-05-13 3:32 Tobin C. Harding
2019-05-13 7:14 ` Greg Kroah-Hartman
2019-05-13 10:39 ` Tobin C. Harding
2019-05-13 16:41 ` Andreas Gruenbacher
2019-05-13 21:40 ` Tobin C. Harding
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='CAHk-=wipiSQ=+dTssFhjYXUS0VgJYRNqy8s_YNTL8HbZ6iKsYg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tobin@kernel.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;
as well as URLs for NNTP newsgroup(s).