From: Joel Becker <jlbec@evilplan.org>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Anthony Iliopoulos <ailiop@suse.com>,
Mark Fasheh <mark@fasheh.com>, akpm <akpm@linux-foundation.org>,
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 04:57:57 +0100 [thread overview]
Message-ID: <ZJuvxQF4epheLig8@ZenIV> (raw)
In-Reply-To: <6d59ab08-070f-1562-2eaa-16b083f1a732@linux.alibaba.com>
Yes, thank you.
Acked-by: Joel Becker <jlbec@evilplan.org>
On Wed, Jun 28, 2023 at 10:30:33AM +0800, Joseph Qi wrote:
> 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(-)
> >
--
prev parent reply other threads:[~2023-06-28 3:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 1:34 [PATCH 0/2] update ocfs2-devel mailing list addresses 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 ` [PATCH 0/2] update ocfs2-devel mailing list addresses Joseph Qi
2023-06-28 3:57 ` Joel Becker [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=ZJuvxQF4epheLig8@ZenIV \
--to=jlbec@evilplan.org \
--cc=ailiop@suse.com \
--cc=akpm@linux-foundation.org \
--cc=joseph.qi@linux.alibaba.com \
--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;
as well as URLs for NNTP newsgroup(s).