From: Steven Rostedt <rostedt@goodmis.org>
To: Shuah <shuah@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
gregkh@linuxfoundation.org, corbet@lwn.net,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, conduct@kernel.org,
tab@lists.linux.dev, Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH] Documentation/CoC: Spell out the TAB role in enforcement decisions
Date: Tue, 4 Mar 2025 16:55:28 -0500 [thread overview]
Message-ID: <20250304165528.2e9b336c@gandalf.local.home> (raw)
In-Reply-To: <2b3aad9e-5288-45d5-bcdd-9dbc4f7298b4@kernel.org>
On Tue, 4 Mar 2025 14:43:13 -0700
Shuah <shuah@kernel.org> wrote:
> > Without an explanation of the intent, the CoC and TAB would appear more
> > opaque, especially given the tags present on v1 that shows the patch has
> > been discussed behind closed doors.
>
> No decisions are made behind the closed doors. As mentioned above, the
> document had inconsistent in when it described the TAB role. This patch
> is fixing the inconsistency.
I guess this should have included a "Fixes" tag and described what it was fixing.
As I was one of the reviewers, I blame myself for not catching that.
-- Steve
>
> >
> >> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> Acked-by: Miguel Ojeda <ojeda@kernel.org>
> >> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> >> Acked-by: Jonathan Corbet <corbet@lwn.net>
> >> Signed-off-by: Shuah Khan <shuah@kernel.org>
> >> ---
next prev parent reply other threads:[~2025-03-04 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 19:48 Shuah Khan
2025-03-04 20:09 ` Laurent Pinchart
2025-03-04 21:43 ` Shuah
2025-03-04 21:55 ` Steven Rostedt [this message]
2025-03-04 23:48 ` Shuah
2025-03-05 9:54 ` Jani Nikula
2025-03-05 15:31 ` Steven Rostedt
2025-03-05 20:08 ` Shuah
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=20250304165528.2e9b336c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=conduct@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=shuah@kernel.org \
--cc=tab@lists.linux.dev \
--cc=workflows@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