From: Thomas Gleixner <tglx@linutronix.de>
To: Fang Xiang <fangxiang3@xiaomi.com>,
maz@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: fangxiang3@xiaomi.com
Subject: Re: [PATCH v2] irqchip/gic-v3-its: Flush ITS tables before writing GITS_BASER<n> registers in non-coherent GIC designs.
Date: Fri, 27 Oct 2023 10:16:57 +0200 [thread overview]
Message-ID: <87v8as32fa.ffs@tglx> (raw)
In-Reply-To: <20231027031007.2088-1-fangxiang3@xiaomi.com>
On Fri, Oct 27 2023 at 11:10, Fang Xiang wrote:
> In non-coherent GIC design, ITS tables should be clean and flushed
> to the PoV of the ITS before writing GITS_BASER<n> registers. And
> hoist the quirked non-shareable attributes earlier to save effort
> in tables setup.
>
> Signed-off-by: Fang Xiang <fangxiang3@xiaomi.com>
Seriously? You claim authorship for a patch which was written by Marc:
https://lore.kernel.org/all/87sf5x6cdu.wl-maz@kernel.org
without even the courtesy of giving him credit via 'Originally-by' ?
That's not how it works.
Thanks,
tglx
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Fang Xiang <fangxiang3@xiaomi.com>,
maz@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: fangxiang3@xiaomi.com
Subject: Re: [PATCH v2] irqchip/gic-v3-its: Flush ITS tables before writing GITS_BASER<n> registers in non-coherent GIC designs.
Date: Fri, 27 Oct 2023 10:16:57 +0200 [thread overview]
Message-ID: <87v8as32fa.ffs@tglx> (raw)
In-Reply-To: <20231027031007.2088-1-fangxiang3@xiaomi.com>
On Fri, Oct 27 2023 at 11:10, Fang Xiang wrote:
> In non-coherent GIC design, ITS tables should be clean and flushed
> to the PoV of the ITS before writing GITS_BASER<n> registers. And
> hoist the quirked non-shareable attributes earlier to save effort
> in tables setup.
>
> Signed-off-by: Fang Xiang <fangxiang3@xiaomi.com>
Seriously? You claim authorship for a patch which was written by Marc:
https://lore.kernel.org/all/87sf5x6cdu.wl-maz@kernel.org
without even the courtesy of giving him credit via 'Originally-by' ?
That's not how it works.
Thanks,
tglx
next prev parent reply other threads:[~2023-10-27 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 3:10 [PATCH v2] irqchip/gic-v3-its: Flush ITS tables before writing GITS_BASER<n> registers in non-coherent GIC designs Fang Xiang
2023-10-27 3:10 ` Fang Xiang
2023-10-27 8:16 ` Thomas Gleixner [this message]
2023-10-27 8:16 ` Thomas Gleixner
2023-10-30 2:05 ` Fang Xiang
2023-10-30 2:05 ` Fang Xiang
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=87v8as32fa.ffs@tglx \
--to=tglx@linutronix.de \
--cc=fangxiang3@xiaomi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
/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.