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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sun, 13 Aug 2023 08:16:50 +0800
From:   Jacky Huang <ychuang570808@...il.com>
To:     Arnd Bergmann <arnd@...db.de>,
        Alessandro Zummo <a.zummo@...ertech.it>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Rob Herring <robh+dt@...nel.org>,
        krzysztof.kozlowski+dt@...aro.org,
        Conor Dooley <conor+dt@...nel.org>
Cc:     linux-rtc@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        mjchen@...oton.com, schung@...oton.com,
        Jacky Huang <ychuang3@...oton.com>
Subject: Re: [RESEND PATCH v2 0/3] Add support for Nuvoton ma35d1 rtc
 controller


On 2023/8/12 下午 04:53, Arnd Bergmann wrote:
> On Wed, Aug 9, 2023, at 03:15, Jacky Huang wrote:
>> From: Jacky Huang <ychuang3@...oton.com>
>>
>> This patch series adds the rtc driver for the nuvoton ma35d1 ARMv8 SoC.
>> It includes DT binding documentation, the ma35d1 rtc driver, and device
>> tree updates.
>>
>> The ma35d1 rtc controller provides real-time and calendar messaging
>> capabilities. It supports programmable time tick and alarm match
>> interrupts. The time and calendar messages are expressed in BCD format.
>>
>> This rtc driver has been tested on the ma35d1 som board with Linux 6.5-rc2.
> Hi Jacky,
>
> I see you added soc@...nel.org to Cc for all three patches, which
> has put them into the patchwork tracker.
>
> Now that the platoform support is merged, I do not pick up patches
> for other subsystems through the soc tree, so please drop the Cc
> here.
>
> You can post the the dts change along with the driver, but the
> correct process is that the subsystem maintainer(s) pick up the
> DT binding and the driver once the review is complete, and then
> you send the dts changes to soc@...nel.org. Depending on the
> platform, there may be a lot of conflicting dts changes, so this
> way you can aggregate any patches for these files before sending
> them to the soc tree for inclusion, while I then merge them
> with all the dts changes for other platforms and any global
> cleanup.
>
>      Arnd


Dear Arnd,


Thank you for the detailed explanation. I now understand how to proceed.

I will remove Cc: soc@...nel.org from here. I apologize for any 
inconvenience

this patch series may have caused you and appreciate your assistance.


Best Regards,

Jacky Huang


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ