mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Anthony Iliopoulos <ailiop@suse.com>,
	Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
	akpm <akpm@linux-foundation.org>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] update ocfs2-devel mailing list addresses
Date: Wed, 28 Jun 2023 10:30:33 +0800	[thread overview]
Message-ID: <6d59ab08-070f-1562-2eaa-16b083f1a732@linux.alibaba.com> (raw)
In-Reply-To: <20230628013437.47030-1-ailiop@suse.com>

Thanks for this work.

Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>

On 6/28/23 9:34 AM, Anthony Iliopoulos wrote:
> The ocfs2-devel mailing list has been migrated to kernel.org, update all
> related kernel documentation pointers to reflect the change.
> 
> Anthony Iliopoulos (2):
>   MAINTAINERS: Update ocfs2-devel mailing list address
>   docs: update ocfs2-devel mailing list address
> 
>  Documentation/ABI/obsolete/o2cb       |  4 ++--
>  Documentation/ABI/removed/o2cb        |  4 ++--
>  Documentation/ABI/stable/o2cb         |  4 ++--
>  Documentation/ABI/testing/sysfs-ocfs2 | 12 ++++++------
>  Documentation/filesystems/dlmfs.rst   |  2 +-
>  Documentation/filesystems/ocfs2.rst   |  2 +-
>  MAINTAINERS                           |  2 +-
>  fs/ocfs2/Kconfig                      |  6 +++---
>  8 files changed, 18 insertions(+), 18 deletions(-)
> 

  parent reply	other threads:[~2023-06-28  2:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  1:34 Anthony Iliopoulos
2023-06-28  1:34 ` [PATCH 1/2] MAINTAINERS: Update ocfs2-devel mailing list address Anthony Iliopoulos
2023-06-28  2:44   ` Randy Dunlap
2023-06-28  8:48     ` Anthony Iliopoulos
2023-06-28  1:34 ` [PATCH 2/2] docs: update " Anthony Iliopoulos
2023-06-28  2:30 ` Joseph Qi [this message]
2023-06-28  3:57   ` [PATCH 0/2] update ocfs2-devel mailing list addresses Joel Becker

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=6d59ab08-070f-1562-2eaa-16b083f1a732@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=ailiop@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=jlbec@evilplan.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    /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
all inboxes | Powered by JetHome®