linux-kernel - Re: media: rcar-csi2: Use common error handling code in rcsi2_parse

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

Message-ID: <aa212ffb-1786-4b86-95cc-f2ee0cd455bf@web.de>
Date: Sat, 16 Mar 2024 13:21:37 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Dan Carpenter <dan.carpenter@...aro.org>,
 Niklas Söderlund <niklas.soderlund@...natech.se>,
 linux-renesas-soc@...r.kernel.org, linux-media@...r.kernel.org,
 kernel-janitors@...r.kernel.org
Cc: Sakari Ailus <sakari.ailus@...ux.intel.com>,
 Geert Uytterhoeven <geert@...ux-m68k.org>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: media: rcar-csi2: Use common error handling code in
 rcsi2_parse_dt()

> I said I would send a couple of these but then Markus went ahead and
> sent the patches that I was going to write...

I dared also to touch some software components.


>                                                And then it was like,
> "Oh, these have some questionable style issues"

The patch review is still evolving, isn't it?


> so it wasn't clear what was happening and I lost track.

I find such information surprising.


There are various source code places left over which could be adjusted somehow.

Some contributors would appreciate further clarifications according to
desirable collateral evolution.

See also:
question about kernel cocci and cleanup.h
2024-03-07
https://lore.kernel.org/cocci/CO1PR11MB49149F1167679926A2917E0997202@CO1PR11MB4914.namprd11.prod.outlook.com/

Regards,
Markus