From: Nelson Johnson <nzjfr547@gmail.com>
To: andriy.shevchenko@intel.com
Cc: hansg@kernel.org, adrian.hunter@intel.com,
ulf.hansson@linaro.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 0/3] mmc: Lenovo N22 Braswell SD slot fixes
Date: Mon, 23 Mar 2026 19:27:35 -0500 [thread overview]
Message-ID: <20260324002735.21092-1-nzjfr547@gmail.com> (raw)
In-Reply-To: <acEScW4vpBvVgkXF@ashevche-desk.local>
On Mon, Mar 23, 2026 at 12:14:09PM +0200, Andy Shevchenko wrote:
> A side note: Your email lost the In-reply-to and possibly other
> headers, so it looks like a new email thread, however by subject
> it seems as a reply into the previous discussion. Check if you
> have nothing wrong with your email setup.
Apologies for the broken threading. It looks like my last reply
did not preserve the expected threading headers on-list. As a
first-time submitter I was not aware of the distinction between
on-list and off-list replies. I will reply to list-archived
messages going forward and double-check the generated headers
before sending.
next prev parent reply other threads:[~2026-03-24 0:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23a36448-9006-47c4-9709-615a889ebd95@kernel.org>
2026-03-21 15:25 ` [PATCH 0/3] mmc: Lenovo N22 Braswell SD slot fixes Nelson Johnson
2026-03-21 16:14 ` Hans de Goede
2026-03-24 0:27 ` Nelson Johnson
2026-03-23 10:14 ` Andy Shevchenko
2026-03-24 0:27 ` Nelson Johnson [this message]
2026-03-16 21:23 Nelson Johnson
2026-03-20 13:27 ` Adrian Hunter
2026-03-20 16:47 ` Nelson Johnson
2026-03-20 17:55 ` Andy Shevchenko
2026-03-20 18:08 ` Andy Shevchenko
2026-03-20 23:07 ` Nelson Johnson
2026-03-21 11:07 ` Hans de Goede
2026-03-24 15:05 ` Adrian Hunter
2026-03-20 17:49 ` Andy Shevchenko
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=20260324002735.21092-1-nzjfr547@gmail.com \
--to=nzjfr547@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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