linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: linux-modules@vger.kernel.org, lucas.de.marchi@gmail.com,
	patchwork-bot@kernel.org, Shuo Wang <wangshuo47@huawei.com>
Cc: hushiyuan@huawei.com
Subject: Re: [PATCH] NEWS: fix typo
Date: Thu,  3 Dec 2020 01:49:35 -0800	[thread overview]
Message-ID: <160698893481.49294.5586143633145480389.b4-ty@intel.com> (raw)
In-Reply-To: <20201125013121.4196-1-wangshuo47@huawei.com>

On Wed, 25 Nov 2020 09:31:21 +0800, Shuo Wang wrote:
> 


Applied, thanks!

[1/1] NEWS: fix typo
      commit: c72433254ee0bda8db5d8d78a643c481a51f88a5

Best regards,
-- 
Lucas De Marchi <lucas.demarchi@intel.com>

  reply	other threads:[~2020-12-03  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25  1:31 [PATCH] NEWS: fix typo Shuo Wang
2020-12-03  9:49 ` Lucas De Marchi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-02 14:03 Shuo Wang

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=160698893481.49294.5586143633145480389.b4-ty@intel.com \
    --to=lucas.demarchi@intel.com \
    --cc=hushiyuan@huawei.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    --cc=patchwork-bot@kernel.org \
    --cc=wangshuo47@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).