From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "keescook@chromium.org" <keescook@chromium.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Brown, Len" <len.brown@intel.com>
Subject: Re: [PATCH v2 1/3] x86: Separate out x86_regset for 32 and 64 bit
Date: Thu, 17 Mar 2022 21:54:52 +0000 [thread overview]
Message-ID: <3ad2e3736c0062edd11960d1f476544e6543eaeb.camel@intel.com> (raw)
In-Reply-To: <202203171427.692F92D7@keescook>
On Thu, 2022-03-17 at 14:33 -0700, Kees Cook wrote:
> I think of "Ack" to mean "I am a maintainer of this area and someone
> can
> carry this instead of it going via my tree". While I certainly poke
> and
> ptrace and x86 a lot, I probably wouldn't Ack in this part of the
> kernel. But it does seem "Reviewed-by" is a stronger signal[1].
I thought I remembered reading in some kernel docs somewhere to demote
reviewed-by's to acks if anything changed, so some credit goes in for
the past work on it. Cannot find anything now, thanks for the
clarification.
next prev parent reply other threads:[~2022-03-17 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 19:20 [PATCH v2 0/3] Regset cleanups Rick Edgecombe
2022-03-17 19:20 ` [PATCH v2 1/3] x86: Separate out x86_regset for 32 and 64 bit Rick Edgecombe
2022-03-17 21:33 ` Kees Cook
2022-03-17 21:54 ` Edgecombe, Rick P [this message]
2022-03-17 19:20 ` [PATCH v2 2/3] x86: Improve formatting of user_regset arrays Rick Edgecombe
2022-03-17 19:20 ` [PATCH v2 3/3] elf: Don't write past end of notes for regset gap Rick Edgecombe
2022-03-17 21:26 ` Kees Cook
2022-03-17 21:53 ` Edgecombe, Rick P
2022-03-18 17:18 ` (subset) " Kees Cook
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=3ad2e3736c0062edd11960d1f476544e6543eaeb.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=len.brown@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=reinette.chatre@intel.com \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
/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).