public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Jens Axboe <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: correct git location for block layer tree
Date: Mon, 3 Nov 2025 15:54:24 +0000	[thread overview]
Message-ID: <6691aedc-de20-4bcc-badc-a0b6e155e0f2@oracle.com> (raw)
In-Reply-To: <d2752a68-929c-46e5-b2b4-e85ac3e6d138@kernel.dk>

On 03/11/2025 15:52, Jens Axboe wrote:
> As part of a recent move go exclusively listing git.kernel.org trees
> for the block and io_uring development, the "BLOCK LAYER" entry wasn't
> updated as it already used git.kernel.org. However, outside of just
> moving from git.kernel.dk to git.kernel.org, the "block" part of the
> trees was also dropped, as the tree serves both block and io_uring
> development trees.
> 
> Fix up the "BLOCK LAYER" entry so they all use the same tree.
> 
> Reported-by: John Garry <john.g.garry@oracle.com>
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> 
> ---

thanks

Reviewed-by: John Garry <john.g.garry@oracle.com>


> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0554bf05b426..b986f4635b7d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4362,7 +4362,7 @@ BLOCK LAYER
>   M:	Jens Axboe <axboe@kernel.dk>
>   L:	linux-block@vger.kernel.org
>   S:	Maintained
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git
>   F:	Documentation/ABI/stable/sysfs-block
>   F:	Documentation/block/
>   F:	block/
> 


      reply	other threads:[~2025-11-03 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 15:52 [PATCH] MAINTAINERS: correct git location for block layer tree Jens Axboe
2025-11-03 15:54 ` John Garry [this message]

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=6691aedc-de20-4bcc-badc-a0b6e155e0f2@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.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