From: <Conor.Dooley@microchip.com>
To: <wsa@kernel.org>, <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 11:17:17 +0000 [thread overview]
Message-ID: <ae44d6ea-fcf6-04ad-311b-a69946201086@microchip.com> (raw)
In-Reply-To: <Yq8DqWEdEEkrAm6H@shikoro>
On 19/06/2022 12:08, Wolfram Sang wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>> 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?
Quite possibly, but no harm in trying to help was the way I saw it!
prev parent reply other threads:[~2022-06-19 11:17 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
2022-06-19 11:17 ` Conor.Dooley [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=ae44d6ea-fcf6-04ad-311b-a69946201086@microchip.com \
--to=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 \
--cc=wsa@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