From: hanzhijian <hanzhijian1991@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: OCTEON: pcie: fix kernel-doc comments
Date: Fri, 21 Aug 2026 17:41:00 -0700 (PDT) [thread overview]
Message-ID: <178735925266.2386114.4269326939882098876@gmail.com> (raw)
In-Reply-To: <20260822002256.2380061-1-hanzhijian@zepp.com>
To clarify the confusion in this thread:
1. <20260822002256.2380061-1-hanzhijian@zepp.com> (the first patch) is valid. Despite what the
Message-ID looks like, its From: address is my correct kernel
contribution address (hanzhijian1991@gmail.com), so the first
retraction below was mistaken.
2. <20260822002543.2381024-1-hanzhijian1991@gmail.com> (the second patch) is a duplicate of the first and
should be ignored.
Please review the first patch. Sorry for the noise.
Han
prev parent reply other threads:[~2026-08-22 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 0:22 [PATCH] MIPS: OCTEON: pcie: fix kernel-doc comments hanzhijian
2026-08-22 0:25 ` hanzhijian
2026-08-22 0:38 ` hanzhijian
2026-08-22 0:26 ` hanzhijian
2026-08-22 0:41 ` hanzhijian [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=178735925266.2386114.4269326939882098876@gmail.com \
--to=hanzhijian1991@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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