Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Dorjoy Chowdhury <dorjoychy111@gmail.com>
Cc: linux-man@vger.kernel.org, brauner@kernel.org, jlayton@kernel.org
Subject: Re: [PATCH v2 2/2] man/man2/openat2.2: Document OPENAT2_REGULAR flag
Date: Sun, 26 Apr 2026 21:15:39 +0200	[thread overview]
Message-ID: <ae5jY4KyRvZWTzTZ@devuan> (raw)
In-Reply-To: <CAFfO_h4cL0nPV8YsSHErJN9fqHy3e4j2C-P-PPUcxr1xAJZ5pQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

Hey Dorjoy,

On 2026-04-26T23:39:29+0600, Dorjoy Chowdhury wrote:
> Hey Alex,
> 
> On Sun, Apr 26, 2026 at 7:03 PM Alejandro Colomar <alx@kernel.org> wrote:
> >
> > Hi Dorjoy,
> >
> > On 2026-04-26T17:14:26+0600, Dorjoy Chowdhury wrote:
> > > Signed-off-by: Dorjoy Chowdhury <dorjoychy111@gmail.com>
> >
> >         Reviewed-by: Alejandro Colomar <alx@kernel.org>
> >
> > Thanks!  Please ping when it's in Linus's tree, so that I'll merge.
> >
> 
> Thanks for reviewing. I should ping after it's in Linus's tree,
> meaning if it's in Linux 7.2 or Linux 7.2-rc1 ?

-rc1 should be fine.  If anything is eventually reverted, we can fix it
here; no problem.

> Sorry I don't quite
> know the workflow.


> Also I guess I need to look into glibc after it
> gets into Linus's tree, right?

I guess once it's in -rc1, you can start discussing a patch there.
I guess they won't merge anything until it's in the final release, but
you could discuss it earlier, so that it lands there soon after
Linux 7.2.


Have a lovely night!
Alex

> 
> Regards,
> Dorjoy

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-04-26 19:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-26 11:14 [PATCH v2 0/2] Document EFTYPE error code and OPENAT2_REGULAR flag Dorjoy Chowdhury
2026-04-26 11:14 ` [PATCH v2 1/2] man/man3/errno.3: Document EFTYPE error code Dorjoy Chowdhury
2026-04-26 12:59   ` Alejandro Colomar
2026-04-27 10:34     ` Florian Weimer
2026-04-27 13:13       ` Alejandro Colomar
2026-04-27 13:29         ` Florian Weimer
2026-04-27 13:33           ` Alejandro Colomar
2026-04-26 11:14 ` [PATCH v2 2/2] man/man2/openat2.2: Document OPENAT2_REGULAR flag Dorjoy Chowdhury
2026-04-26 13:03   ` Alejandro Colomar
2026-04-26 17:39     ` Dorjoy Chowdhury
2026-04-26 19:15       ` Alejandro Colomar [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=ae5jY4KyRvZWTzTZ@devuan \
    --to=alx@kernel.org \
    --cc=brauner@kernel.org \
    --cc=dorjoychy111@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=linux-man@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