lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2beb4f12-c485-4af5-86ef-a481f6f7ecae@ti.com>
Date: Tue, 27 Aug 2024 10:24:39 +0530
From: Beleswar Prasad Padhi <b-padhi@...com>
To: Krzysztof Kozlowski <krzk@...nel.org>, <nm@...com>, <vigneshr@...com>,
        <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>
CC: <u-kumar1@...com>, <tony@...mide.com>, <bb@...com>, <d-gole@...com>,
        <afd@...com>, <hnagalla@...com>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 1/7] arm64: dts: ti: k3-j7200-som-p0: Change timer
 nodes status to reserved


On 26/08/24 18:07, Krzysztof Kozlowski wrote:
> On 26/08/2024 12:54, Krzysztof Kozlowski wrote:
>> On 26/08/2024 12:48, Beleswar Padhi wrote:
>>> The remoteproc firmware of R5F in the MAIN voltage domain use timers.
>>> Therefore, change the status of the timer nodes to "reserved" to avoid
>>> any clash. Usage is described as below:
>>>
>>> 	+===================+==========================+
>>> 	|  Remoteproc node  |        Timer Node        |
>>> 	+===================+==========================+
>>> 	| main_r5fss0_core0 | main_timer0, main_timer2 |
>>> 	+-------------------+--------------------------+
>>> 	| main_r5fss0_core1 | main_timer1              |
>>> 	+-------------------+--------------------------+
>>>
>>> Fixes: c8a28ed4837c ("arm64: dts: ti: k3-j7200: Add general purpose timers")
>>> Signed-off-by: Beleswar Padhi <b-padhi@...com>
>> You keep sending the same. Where is the changelog? Why so many same
>> patchsets? Why so many resends without changes?
> OK, now cover letter came and I see the changelog. Some hickup on mail
> servers.


I understand the mistake. From next time, will mention changelogs in 
patches as well as cover letter.

>
> Best regards,
> Krzysztof
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ