linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: ceph-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 pdonnell@redhat.com, amarkuze@redhat.com, Slava.Dubeyko@ibm.com,
	 vdubeyko@redhat.com
Subject: Re: [PATCH] ceph: add in MAINTAINERS bug tracking system info
Date: Thu, 4 Sep 2025 12:45:46 +0200	[thread overview]
Message-ID: <CAOi1vP8Og5phUw3LO3Fv3yfnSSx3FhuSmj7j4pHrF00t-MGS9w@mail.gmail.com> (raw)
In-Reply-To: <20250902200957.126211-2-slava@dubeyko.com>

On Tue, Sep 2, 2025 at 10:10 PM Viacheslav Dubeyko <slava@dubeyko.com> wrote:
>
> From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
>
> CephFS kernel client depends on declaractions in
> include/linux/ceph/. So, this folder with Ceph
> declarations should be mentioned for CephFS kernel
> client. Also, this patch adds information about

Hi Slava,

This argument can be extended to everything that falls under CEPH
COMMON CODE (LIBCEPH) entry and then be applied to RBD as well.
Instead of duplicating include/linux/ceph/ path, I'd suggest replacing
Xiubo with yourself and/or Alex under LIBCEPH and CEPH entries so that
you get CCed on all patches.  That would appropriately reflect the
status quo IMO.

> Ceph bug tracking system.
>
> Signed-off-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
> cc: Alex Markuze <amarkuze@redhat.com>
> cc: Ilya Dryomov <idryomov@gmail.com>
> cc: Ceph Development <ceph-devel@vger.kernel.org>
> ---
>  MAINTAINERS | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6dcfbd11efef..70fc6435f784 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5625,6 +5625,7 @@ M:        Xiubo Li <xiubli@redhat.com>
>  L:     ceph-devel@vger.kernel.org
>  S:     Supported
>  W:     http://ceph.com/
> +B:     https://tracker.ceph.com/

Let's add this for RADOS BLOCK DEVICE (RBD) entry too.

Thanks,

                Ilya

  parent reply	other threads:[~2025-09-04 10:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 20:09 [PATCH] ceph: add in MAINTAINERS bug tracking system info Viacheslav Dubeyko
2025-09-03  8:16 ` Alex Markuze
2025-09-04 10:45 ` Ilya Dryomov [this message]
2025-09-04 18:36   ` vdubeyko

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=CAOi1vP8Og5phUw3LO3Fv3yfnSSx3FhuSmj7j4pHrF00t-MGS9w@mail.gmail.com \
    --to=idryomov@gmail.com \
    --cc=Slava.Dubeyko@ibm.com \
    --cc=amarkuze@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=pdonnell@redhat.com \
    --cc=slava@dubeyko.com \
    --cc=vdubeyko@redhat.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;
as well as URLs for NNTP newsgroup(s).