From: Brian Norris <briannorris@chromium.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
Justin Stitt <justinstitt@google.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] cpumask: Switch from inline to __always_inline
Date: Mon, 8 Jul 2024 12:46:58 -0700 [thread overview]
Message-ID: <ZoxCMp_ZQ-Su-r0D@google.com> (raw)
In-Reply-To: <ZoWhPFJIvGpMGKm4@yury-ThinkPad>
On Wed, Jul 03, 2024 at 12:06:36PM -0700, Yury Norov wrote:
> Hi Brian,
>
> I never received the original email, only this reply, and can't recover
> any context.
That's unfortunate! I don't know what happened there. My usual culprit
would be something in the DMARC/DKIM/SPF spam-filtering space, but:
(a) it made it to the archives, such as:
https://lore.kernel.org/all/20240514204910.1383909-1-briannorris@chromium.org/
and
(b) I don't see any red flags in the mail headers on lore
(https://lore.kernel.org/all/20240514204910.1383909-1-briannorris@chromium.org/raw)
such as DKIM, SPF, or DMARC failures.
Anyway, if you just want the original mail contents that I stripped from
my "ping" reply, they are available in the above archives.
Since I don't know what went wrong on v1, I don't really know what to
fix on a v2. But if I send a v2 and don't hear anything for a while ...
I suppose I can "ping" again!
Regards,
Brian
prev parent reply other threads:[~2024-07-08 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 20:49 [PATCH] cpumask: Switch from inline to __always_inline Brian Norris
2024-06-25 18:27 ` Brian Norris
2024-07-03 19:06 ` Yury Norov
2024-07-03 19:57 ` Nathan Chancellor
2024-07-08 19:41 ` Brian Norris
2024-07-08 20:13 ` Yury Norov
2024-07-08 19:46 ` Brian Norris [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=ZoxCMp_ZQ-Su-r0D@google.com \
--to=briannorris@chromium.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=yury.norov@gmail.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