public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: wens@csie.org
Cc: jernej.skrabec@gmail.com, samuel@sholland.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH] arm64: dts: allwinner: Add cache information to the SoC dtsi for H6
Date: Tue, 28 May 2024 18:02:52 +0200	[thread overview]
Message-ID: <803a939c62b3ac4ced7ac49f18efd723@manjaro.org> (raw)
In-Reply-To: <CAGb2v64ETOtHxQf1D9n+c9bGivsRTC=O8swDru+2cX2UT=o0qw@mail.gmail.com>

Hello Chen-Yu,

On 2024-05-28 17:56, Chen-Yu Tsai wrote:
> On Tue, May 28, 2024 at 11:46 PM Chen-Yu Tsai <wens@csie.org> wrote:
>> 
>> On Sun, 28 Apr 2024 13:40:36 +0200, Dragan Simic wrote:
>> > Add missing cache information to the Allwinner H6 SoC dtsi, to allow
>> > the userspace, which includes lscpu(1) that uses the virtual files provided
>> > by the kernel under the /sys/devices/system/cpu directory, to display the
>> > proper H6 cache information.
>> >
>> > Adding the cache information to the H6 SoC dtsi also makes the following
>> > warning message in the kernel log go away:
>> >
>> > [...]
>> 
>> Applied to sunxi/dt-for-6.11 in sunxi/linux.git, thanks!
>> 
>> [1/1] arm64: dts: allwinner: Add cache information to the SoC dtsi for 
>> H6
>>       https://git.kernel.org/sunxi/linux/c/c8240e4b0fd2
> 
> OK, that's weird. Somehow b4 thought this patch was v2 of the A64 patch 
> [1].
> Looks like they are threaded together because this patch has 
> "In-Reply-To".
> 
> Please avoid it in the future.

I'm sorry for that.  I noticed that back when I sent the patches to the
mailing list, but didn't want to make some noise about that.  The root
cause was some missing configuration for "git send-email", which 
resulted
in adding troublesome threading-related headers to the messages for the
individual .patch files that in fact were correctly created by running
"git format-patch".

Do I need to resend the patches?

  reply	other threads:[~2024-05-28 16:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28 11:40 [PATCH] arm64: dts: allwinner: Add cache information to the SoC dtsi for A64 Dragan Simic
2024-04-28 11:40 ` [PATCH] arm64: dts: allwinner: Add cache information to the SoC dtsi for H6 Dragan Simic
2024-04-28 16:21   ` Jernej Škrabec
2024-04-29 23:10   ` Andre Przywara
2024-04-30  0:01     ` Dragan Simic
2024-04-30 10:46       ` Andre Przywara
2024-04-30 11:10         ` Dragan Simic
2024-05-01  9:30           ` Andre Przywara
2024-05-03  9:13             ` Dragan Simic
2024-05-28 15:46   ` Chen-Yu Tsai
2024-05-28 15:56     ` Chen-Yu Tsai
2024-05-28 16:02       ` Dragan Simic [this message]
2024-05-28 16:06         ` Chen-Yu Tsai
2024-05-28 16:17     ` Chen-Yu Tsai
2024-05-28 16:10   ` Chen-Yu Tsai
2024-04-28 16:19 ` [PATCH] arm64: dts: allwinner: Add cache information to the SoC dtsi for A64 Jernej Škrabec
2024-04-29 10:33 ` Andre Przywara
2024-04-29 13:51   ` Dragan Simic
2024-05-28 16:10 ` Chen-Yu Tsai
2024-05-28 16:16   ` Chen-Yu Tsai

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=803a939c62b3ac4ced7ac49f18efd723@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox