From: Daniel Thompson <daniel.thompson@linaro.org>
To: wengjianfeng <samirweng1979@163.com>
Cc: jason.wessel@windriver.com, dianders@chromium.org,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
wengjianfeng <wengjianfeng@yulong.com>
Subject: Re: [PATCH] kernel: debug: fix typo issue
Date: Wed, 3 Feb 2021 11:55:55 +0000 [thread overview]
Message-ID: <20210203115555.amlmxszvfidjic46@maple.lan> (raw)
In-Reply-To: <20210203193609.00007678@163.com>
On Wed, Feb 03, 2021 at 07:36:09PM +0800, wengjianfeng wrote:
> On Wed, 3 Feb 2021 11:23:59 +0000
> Daniel Thompson <daniel.thompson@linaro.org> wrote:
>
> > On Wed, Feb 03, 2021 at 04:10:34PM +0800, samirweng1979 wrote:
> > > From: wengjianfeng <wengjianfeng@yulong.com>
> > >
> > > change 'regster' to 'register'.
> > >
> > > Signed-off-by: wengjianfeng <wengjianfeng@yulong.com>
> >
> > It looks like the Subject line might not be correct for this patch?
> >
> > Is it really the first time this patch has been circulated or should
> > it have been tagged RESEND or v2?
>
> The patch was first sent on January 25, but nobody relply me, so I
> just resend the patch, and the patch is the same as last time,does I
> need add RESEND tag? thanks.
Yes. When resending a patch adding a RESEND is a useful courtesy to let
the maintainer know why they have received two copies of the same patch
(and to make clear that the content is the same).
Daniel.
next prev parent reply other threads:[~2021-02-03 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 8:10 [PATCH] kernel: debug: fix typo issue samirweng1979
2021-02-03 11:23 ` Daniel Thompson
2021-02-03 11:36 ` wengjianfeng
2021-02-03 11:55 ` Daniel Thompson [this message]
2021-02-04 15:26 ` Daniel Thompson
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=20210203115555.amlmxszvfidjic46@maple.lan \
--to=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=samirweng1979@163.com \
--cc=wengjianfeng@yulong.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.