From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
stable <stable@vger.kernel.org>,
Jarkko Sakkinen <jarkko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
keyrings@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] assoc_array: Fix BUG_ON during garbage collect
Date: Thu, 02 Jun 2022 10:05:00 -0700 [thread overview]
Message-ID: <87r147yp1f.fsf@stepbren-lnx.us.oracle.com> (raw)
In-Reply-To: <CAHk-=wjHHg_buCqw=Q2OtRWoFpD67OxsQ0jMzao+6rGM6hRE0A@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, Jun 1, 2022 at 3:00 PM Stephen Brennan
> <stephen.s.brennan@oracle.com> wrote:
>>
>> Just wanted to check on this patch as the 5.19 window closes. David, are
>> you planning on taking this through a particular tree, or is the ask for
>> Linus to pick it directly?
>
> Ok, picked up directly.
>
> These fall through the cracks partly because it's not obvious what
> they are for. Sometimes I get pull requests from DavidH, and sometimes
> I get random patches, and while the pull requests are fairly
> unambiguous ("please pull") the same is not necessarily true of the
> patches. Are they for discussion, an RFC, or fro applying...
I understand the confusion, thanks for taking this up!
Stephen
>
> So then I pretty much guess.
>
> Linus
next prev parent reply other threads:[~2022-06-02 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 8:50 [PATCH] assoc_array: Fix BUG_ON during garbage collect David Howells
2022-05-19 22:17 ` Jarkko Sakkinen
2022-05-23 17:39 ` Stephen Brennan
2022-06-01 21:59 ` Stephen Brennan
2022-06-02 1:31 ` Linus Torvalds
2022-06-02 17:05 ` Stephen Brennan [this message]
2022-06-01 22:41 ` Eric Biggers
2022-06-01 23:03 ` Stephen Brennan
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=87r147yp1f.fsf@stepbren-lnx.us.oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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