From: Wolfram Sang <wsa@kernel.org>
To: Conor.Dooley@microchip.com
Cc: lijessen2016@gmail.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, root@laptop-706cegjt.localdomain
Subject: Re: [PATCH] Print some info into ring-buffer during loading
Date: Sun, 19 Jun 2022 13:08:25 +0200 [thread overview]
Message-ID: <Yq8DqWEdEEkrAm6H@shikoro> (raw)
In-Reply-To: <9b94e885-be5f-3548-67ed-d79c6e7c22e0@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 198 bytes --]
> Hey Jessen Li/Jason-Lee,
> (I hope one of those is your name, sorry if it isn't - just feels weird
> addressing a username like "root" haha.
I'd think sending this patch out was unintentional?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-19 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 8:32 [PATCH] Print some info into ring-buffer during loading root
2022-06-19 10:59 ` Conor.Dooley
2022-06-19 11:08 ` Wolfram Sang [this message]
2022-06-19 11:17 ` Conor.Dooley
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=Yq8DqWEdEEkrAm6H@shikoro \
--to=wsa@kernel.org \
--cc=Conor.Dooley@microchip.com \
--cc=lijessen2016@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@laptop-706cegjt.localdomain \
/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