public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Chan <ericchancf@google.com>
To: parri.andrea@gmail.com
Cc: aou@eecs.berkeley.edu, ericchancf@google.com,
	linux-kernel@vger.kernel.org,  linux-riscv@lists.infradead.org,
	palmer@dabbelt.com, paul.walmsley@sifive.com
Subject: Re: [PATCH v5 4/4] riscv/barrier: Resolve checkpatch.pl error
Date: Sat, 17 Feb 2024 13:07:10 +0000	[thread overview]
Message-ID: <20240217130710.3566812-1-ericchancf@google.com> (raw)
In-Reply-To: <Zc/OGnjVKcCuKNA5@andrea>

Hi Andrea,

Thank you very much for patiently reviewing and pointing out areas for improvement.
I also appreciate your kindness.
This is actually my second time submitting an upstream patch,
and the first time submitting multiple patches.
There are still many shortcomings, even though I carefully read the documentation
and refer other submissions before submitting my changes.

Once again, thank you for reviewing and providing such friendly suggestions.

Sincerely,
  Eric Chan

      reply	other threads:[~2024-02-17 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 22:38 [PATCH v5 0/4] riscv/barrier: tidying up barrier-related macro Eric Chan
2024-02-13 22:39 ` [PATCH v5 1/4] riscv/barrier: Define __{mb,rmb,wmb} Eric Chan
2024-02-16 20:30   ` Andrea Parri
2024-02-13 22:39 ` [PATCH v5 2/4] riscv/barrier: Define RISCV_FULL_BARRIER Eric Chan
2024-02-13 22:39 ` [PATCH v5 3/4] riscv/barrier: Consolidate fence definitions Eric Chan
2024-02-13 22:40 ` [PATCH v5 4/4] riscv/barrier: Resolve checkpatch.pl error Eric Chan
2024-02-16 21:05   ` Andrea Parri
2024-02-17 13:07     ` Eric Chan [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=20240217130710.3566812-1-ericchancf@google.com \
    --to=ericchancf@google.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=parri.andrea@gmail.com \
    --cc=paul.walmsley@sifive.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