public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: linux-man@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [dramforever@live.com: [PATCH] man/man5/proc_pid.5: Clarify which user namespace affects permissions]
Date: Wed, 18 Mar 2026 02:59:42 +0100	[thread overview]
Message-ID: <aboGopJ4ismAmjFM@devuan> (raw)
In-Reply-To: <940af389-453f-49ca-b412-0c5c2937748a@iscas.ac.cn>

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

Hi Vivian,

On 2026-03-18T09:43:07+0800, Vivian Wang wrote:
> On 3/18/26 08:56, Alejandro Colomar wrote:
> 
> > Hi Vivian,
> >
> > Can you please confirm this is you?  I received this patch from an
> > address that doesn't match the one I see in your kernel commits, and
> > when I replied to <dramforever@live.com>, the message bounced.  I'm just
> > checking.  See patch from the @live.com address below.
> 
> Hi, Alejandro,
> 
> This is me.

Thanks for confirming!  :)

> Apologies for the confusion. My idea was to use my personal email
> (dramforever@live.com) for dayjob-related stuff, and employer email
> (@iscas.ac.cn) for work-related stuff.
> 
> I've started signing off as "Vivian Wang <dramforever@live.com>" in
> OpenSBI first, before being employed at ISCAS (see [1], firstly done in
> [2] after someone complained about me just signing off as "dramforever
> <dramforever@live.com>"). In June 2025 I was hired by ISCAS and started
> doing primarily kernel work, which was probably where you saw this.
> 
> I did not realize that apparently kernel.org mail bounces on my free
> Outlook email - I wasn't even getting it in my spam box. Unfortunately I
> don't think I have much control over the behavior of Microsoft's Outlook
> servers.
> 
> Next time I will use a different personal address - with a reply from my
> apparently more well known @iscas.ac.cn address vouching for its
> authenticity, to avoid confusion.

No problem; I'm fine with your personal address.  (At least, if it
didn't bounce; that's a problem.)

So, I was saying I have applied the patch.  Thanks!  :-)

> 
> [1]: https://lore.kernel.org/opensbi/?q=f%3A%22Vivian+Wang+%3Cdramforever%22
> [2]: https://lore.kernel.org/opensbi/TYYP286MB1439C5C64BCF8E9DB7883772C69F9@TYYP286MB1439.JPNP286.PROD.OUTLOOK.COM/
> 
> >
> > Have a lovely night!
> > Alex
> 
> Thank you.
> 
> Vivian "dramforever" Wang

:)

Cheers,
Alex

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

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

      reply	other threads:[~2026-03-18  1:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18  0:56 [dramforever@live.com: [PATCH] man/man5/proc_pid.5: Clarify which user namespace affects permissions] Alejandro Colomar
2026-03-18  1:43 ` Vivian Wang
2026-03-18  1:59   ` 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=aboGopJ4ismAmjFM@devuan \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=wangruikang@iscas.ac.cn \
    /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