public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: "Yan Zheng(严政)" <zhengyan@asrmicro.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Gao Meitao(高玫涛)" <meitaogao@asrmicro.com>,
	"\"Zhou Qiao(周侨)\"" <qiaozhou@asrmicro.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"\"Zhang Zhizhou(张治洲)\"" <zhizhouzhang@asrmicro.com>
Subject: Re: [PATCH v2] irqchip/gic-v3: workaround for ASR8601 when reading mpidr
Date: Tue, 30 May 2023 08:15:47 +0100	[thread overview]
Message-ID: <87r0qyjnmk.wl-maz@kernel.org> (raw)
In-Reply-To: <6452e00de4e446ddb25588e29fa9e768@exch03.asrmicro.com>

On Tue, 30 May 2023 07:07:21 +0100,
Yan Zheng(严政) <zhengyan@asrmicro.com> wrote:
> 
> > I came up with the following patch, which keeps the workaround *in
> > a single spot*.
> > 
> > Let me know if that works for you.
> > 
> > 	M.
> > 
> 
> Really thanks for your help, this patch works well for us.
> My previous patch was too ugly, this one looks better. I didn't find this good solution.
> Should I send a patch for v3, considering that you're the author?

See [1]. I've split the refactoring in its own patch, and kept your
authorship for what is left of the workaround code.

No need to resend, I'll queue that for 6.5.

	M.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=irq/gic-v3-asr8601

-- 
Without deviation from the norm, progress is not possible.

      reply	other threads:[~2023-05-30  7:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  7:55 [PATCH] irqchip/gic-v3: workaround for ASR8601 when reading mpidr zhengyan
2023-05-17  8:32 ` Marc Zyngier
2023-05-17 10:45   ` Yan Zheng(严政)
2023-05-17 12:59     ` Marc Zyngier
2023-05-18  3:15       ` Yan Zheng(严政)
2023-05-18  7:23         ` Marc Zyngier
2023-05-22 11:06 ` [PATCH v2] " zhengyan
2023-05-29 15:02   ` Marc Zyngier
2023-05-30  6:07     ` Yan Zheng(严政)
2023-05-30  7:15       ` Marc Zyngier [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=87r0qyjnmk.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meitaogao@asrmicro.com \
    --cc=qiaozhou@asrmicro.com \
    --cc=tglx@linutronix.de \
    --cc=zhengyan@asrmicro.com \
    --cc=zhizhouzhang@asrmicro.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