linux-kernel - Re: [PATCH v3 3/5] staging: vchiq: Move vchiq char driver to its own file

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <3adbf977-3155-753d-2f81-51a375bce35d@i2se.com>
Date:   Sun, 11 Jul 2021 12:35:29 +0200
From:   Stefan Wahren <stefan.wahren@...e.com>
To:     Ojaswin Mujoo <ojaswin98@...il.com>, nsaenz@...nel.org
Cc:     gregkh@...uxfoundation.org, arnd@...db.de,
        dan.carpenter@...cle.com, phil@...pberrypi.com,
        bcm-kernel-feedback-list@...adcom.com,
        linux-arm-kernel@...ts.infradead.org,
        linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/5] staging: vchiq: Move vchiq char driver to its own
 file

Am 04.07.21 um 17:58 schrieb Ojaswin Mujoo:
> Split the initialization code of vchiq char driver and device files from
> that of vchiq platform. The char driver code now resides in vchiq_dev.c
> and the platform code resides in the original vchiq_arm.c file.
>
> This commit focuses on separating the code into different files while
> maintaining the same functionality. It does not completely decouple them
> as the cdev init code is still called from the platform's vchiq_probe()
> function.
>
> Signed-off-by: Ojaswin Mujoo <ojaswin98@...il.com>
Reviewed-by: Stefan Wahren <stefan.wahren@...e.com>