>From: Markus Elfring <Markus.Elfring@xxxxxx> >Sent: 2023年7月18日 1:26 >To: Ming Qian <ming.qian@xxxxxxx>; linux-media@xxxxxxxxxxxxxxx; kernel- >janitors@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; dl-linux-imx ><linux-imx@xxxxxxx>; kernel@xxxxxxxxxxxxxx; Fabio Estevam ><festevam@xxxxxxxxx>; Hans Verkuil <hverkuil-cisco@xxxxxxxxx>; Mauro >Carvalho Chehab <mchehab@xxxxxxxxxx>; Nicolas Dufresne ><nicolas@xxxxxxxxxxxx>; Rob Herring <robh+dt@xxxxxxxxxx>; Sascha Hauer ><s.hauer@xxxxxxxxxxxxxx>; Shawn Guo <shawnguo@xxxxxxxxxx>; Tao Jiang ><tao.jiang_2@xxxxxxx>; X.H. Bao <xiahong.bao@xxxxxxx>; Eagle Zhou ><eagle.zhou@xxxxxxx> >Cc: LKML <linux-kernel@xxxxxxxxxxxxxxx> >Subject: [EXT] Re: [PATCH] media: amphion: fix some issues reported by >coverity > >Caution: This is an external email. Please take care when clicking links or >opening attachments. When in doubt, report the message using the 'Report >this email' button > > >> CHECKED_RETURN: 4 case >> REVERSE_INULL: 2 case >> UNINIT: 6 case >> UNUSED_VALUE: 1 case > >How does such a change combination fit to the development requirement >“Solve only one problem per patch.”? > >See also: >https://git.ker/ >nel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git%2Ft >ree%2FDocumentation%2Fprocess%2Fsubmitting-patches.rst%3Fh%3Dv6.5- >rc2%23n81&data=05%7C01%7Cming.qian%40nxp.com%7C94575f499df74c702 >d8308db86ead678%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63 >8252115406304424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi >LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sd >ata=nr7bqZMPNvrECSOMJsCzn3aU8UWdinBG4sHRRGRJJ1E%3D&reserved=0 > > >Will further imperative change descriptions become more helpful? > >Regards, >Markus Hi Markus, Thanks for your comments, I'll split this patch into 4 patches, one topic one patch. Ming
