From: "Ariel Otilibili-Anieli" <Ariel.Otilibili-Anieli@eurecom.fr>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: "Paul Moore" <paul@paul-moore.com>,
linux-security-module@vger.kernel.org,
"Andrew G . Morgan" <morgan@kernel.org>
Subject: Re: [PATCH 1/1] uapi: fix broken link in linux/capability.h
Date: Wed, 02 Jul 2025 12:05:36 +0200 [thread overview]
Message-ID: <1ad13b-68650480-81f-51fddb80@179270172> (raw)
In-Reply-To: <aGSXgF797s+Oz4C5@mail.hallyn.com>
Hi Serge, hi Paul,
On Wednesday, July 02, 2025 04:20 CEST, "Serge E. Hallyn" <serge@hallyn.com> wrote:
> On Tue, Jul 01, 2025 at 10:05:45PM -0400, Paul Moore wrote:
> > On Jun 29, 2025 Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr> wrote:
> > > Signed-off-by: Ariel Otilibili <ariel.otilibili-anieli@eurecom.fr>
> > > Acked-by: Andrew G. Morgan <morgan@kernel.org>
> >
> > My personal preference would be for a commit description that doesn't
> > wrap when running 'git log' on a 80 char wide terminal, but ultimately
>
> Agreed. Would you mind updating that, and then I'll pull it in?
Sure, there you are: https://lore.kernel.org/all/20250702100021.1849243-2-ariel.otilibili-anieli@eurecom.fr/
>
> thanks,
> -serge
>
> > that is Serge's call to make. Otherwise, the updated URL looks good to
> > me.
> >
> > Reviewed-by: Paul Moore <paul@paul-moore.com>
Thanks for your feedback,
Ariel
next prev parent reply other threads:[~2025-07-02 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 12:03 [PATCH 0/1] uapi: fix broken link in linux/capability.h Ariel Otilibili
2025-06-29 12:03 ` [PATCH 1/1] " Ariel Otilibili
2025-06-29 14:27 ` Andrew G. Morgan
2025-06-29 23:16 ` Ariel Otilibili-Anieli
2025-07-02 2:05 ` Paul Moore
2025-07-02 2:20 ` Serge E. Hallyn
2025-07-02 10:05 ` Ariel Otilibili-Anieli [this message]
2025-07-05 0:25 ` sergeh
2025-07-02 10:00 ` [PATCH v2 0/1] " Ariel Otilibili
2025-07-02 10:00 ` [PATCH v2 1/1] " Ariel Otilibili
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=1ad13b-68650480-81f-51fddb80@179270172 \
--to=ariel.otilibili-anieli@eurecom.fr \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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