From: "Günther Noack" <gnoack@google.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH v2 4/5] landlock.7, landlock_*.2: Document Landlock ABI version 4
Date: Tue, 23 Jul 2024 12:24:18 +0200 [thread overview]
Message-ID: <Zp-E0ucdsGU71Som@google.com> (raw)
In-Reply-To: <ljaijaj3fv6ye5plzma27r7fej2q3z4endo7s5aksm26pc44vy@p2mgcdz3l75u>
On Mon, Jul 22, 2024 at 11:00:13PM +0200, Alejandro Colomar wrote:
> I've applied patches 1, 2, and 3. I applied some tweaks to 3, which
> might be the reason why this doesn't apply. Would you mind rebasing
> 4 and 5? Thanks!
Thanks for the fixes with \% and \~, I did't know I could do this.
I re-sent it as V3 with patches 4/5 and 5/5,
it merged cleanly using:
git rebase --onto master HEAD^^ my-branch
Thank you for the review at such a late hour! ;-)
—Günther
next prev parent reply other threads:[~2024-07-23 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 13:37 [PATCH v2 0/5] landlock*: Bring documentation up to date Günther Noack
2024-07-19 13:37 ` [PATCH v2 1/5] landlock.7, landlock_*.2: wfix Günther Noack
2024-07-22 20:52 ` Alejandro Colomar
2024-07-19 13:37 ` [PATCH v2 2/5] landlock_create_ruleset.2: Update docs for landlock_ruleset_attr Günther Noack
2024-07-22 20:49 ` Alejandro Colomar
2024-07-19 13:38 ` [PATCH v2 3/5] landlock_add_rule.2: Document missing reason for EINVAL Günther Noack
2024-07-19 13:38 ` [PATCH v2 4/5] landlock.7, landlock_*.2: Document Landlock ABI version 4 Günther Noack
2024-07-22 21:00 ` Alejandro Colomar
2024-07-23 10:24 ` Günther Noack [this message]
2024-07-19 13:38 ` [PATCH v2 5/5] landlock.7: Document Landlock ABI version 5 (IOCTL) Günther Noack
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=Zp-E0ucdsGU71Som@google.com \
--to=gnoack@google.com \
--cc=alx@kernel.org \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-man@vger.kernel.org \
--cc=mic@digikod.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.