public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Josh Law <hlcj1234567@gmail.com>
Cc: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Vlastimil Babka <vbabka@suse.com>,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Josh Law <objecting@objecting.org>,
	mm-commits@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	"David Hildenbrand (Arm)" <david@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: add Josh Law as reviewer for library code
Date: Fri, 13 Mar 2026 10:06:44 -0600	[thread overview]
Message-ID: <9d8205fe-c788-429a-985b-8472217dbe32@kernel.dk> (raw)
In-Reply-To: <8bc3ea9f-4e56-4e41-8cf6-97e3b5a45b31@gmail.com>

On 3/13/26 10:00 AM, Josh Law wrote:
> Thank you guys for the context and the history. I understand now why
> my request was premature and how it looks from a security and
> procedural standpoint. I appreciate you taking the time to explain the
> 'Jia Tan' caution, it makes total sense why the bar is so high.
> 
> I'm going to take the 'no rush' advice to heart. I'll focus on the
> technical work, learn the etiquette, and prove myself through quality
> contributions over time. Thank you for not being super mad

That is the way! Just keep at it, it's a long road.

-- 
Jens Axboe

  reply	other threads:[~2026-03-13 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260307221931.2848601-1-objecting@objecting.org>
     [not found] ` <3cd25de5-3737-49f4-aa8b-eaaee471af50@lucifer.local>
     [not found]   ` <ee644e1b-5759-477f-8aec-35c91a5a938e@suse.com>
     [not found]     ` <20260307222154.2848660-1-objecting@objecting.org>
     [not found]       ` <667b75ad-bce9-4997-8ebf-8077952c2797@gmail.com>
2026-03-13 15:00         ` [PATCH] MAINTAINERS: add Josh Law as reviewer for library code Christian Brauner
2026-03-13 15:33           ` Christian Brauner
2026-03-13 15:48             ` Lorenzo Stoakes (Oracle)
2026-03-13 15:51               ` Josh Law
2026-03-13 15:56                 ` Lorenzo Stoakes (Oracle)
2026-03-13 15:56                 ` Jens Axboe
2026-03-13 16:00                   ` Josh Law
2026-03-13 16:06                     ` Jens Axboe [this message]
2026-03-13 15:52             ` Darrick J. Wong
2026-03-13 15:54               ` Josh Law

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=9d8205fe-c788-429a-985b-8472217dbe32@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=hlcj1234567@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=objecting@objecting.org \
    --cc=vbabka@suse.com \
    /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