From: Markus Elfring <Markus.Elfring@web.de>
To: "Dan Carpenter" <dan.carpenter@linaro.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
kernel-janitors@vger.kernel.org
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: media: rcar-csi2: Use common error handling code in rcsi2_parse_dt()
Date: Sat, 16 Mar 2024 13:21:37 +0100 [thread overview]
Message-ID: <aa212ffb-1786-4b86-95cc-f2ee0cd455bf@web.de> (raw)
In-Reply-To: <0b77e146-df2f-4fe1-a4e8-206a62a5ac59@moroto.mountain>
> 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
next prev parent reply other threads:[~2024-03-16 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 12:10 [PATCH] media: rcar-csi2: Use common error handling code in rcsi2_parse_dt() Markus Elfring
2024-03-01 13:05 ` Geert Uytterhoeven
2024-03-01 13:42 ` Dan Carpenter
2024-03-03 8:36 ` Markus Elfring
2024-03-04 10:48 ` Sakari Ailus
2024-03-04 11:16 ` Dan Carpenter
2024-03-16 9:46 ` Niklas Söderlund
2024-03-16 9:54 ` Dan Carpenter
2024-03-16 10:18 ` Niklas Söderlund
2024-03-16 12:21 ` Markus Elfring [this message]
2024-03-01 13:15 ` Laurent Pinchart
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=aa212ffb-1786-4b86-95cc-f2ee0cd455bf@web.de \
--to=markus.elfring@web.de \
--cc=dan.carpenter@linaro.org \
--cc=geert@linux-m68k.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@linux.intel.com \
/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