From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
"Alan Cox" <alan@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Daeseok Youn" <daeseok.youn@gmail.com>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Geliang Tang" <geliangtang@gmail.com>,
"Amitoj Kaur Chawla" <amitoj1606@gmail.com>,
"Georgiana Chelu" <georgiana.chelu93@gmail.com>,
"simran singhal" <singhalsimran0@gmail.com>,
"Julia Lawall" <julia.lawall@lip6.fr>,
"Hans de Goede" <hdegoede@redhat.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Hans Verkuil" <hans.verkuil@cisco.com>,
"Guru Das Srinagesh" <gurooodas@gmail.com>,
"Arushi Singhal" <arushisinghal19971997@gmail.com>,
"Paolo Cretaro" <melko@frugalware.org>,
"Joe Perches" <joe@perches.com>,
"Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>,
"Colin Ian King" <colin.king@canonical.com>,
"Thomas Meyer" <thomas@m3y3r.de>, "Shy More" <smklearn@gmail.com>,
"Varsha Rao" <rvarsha016@gmail.com>,
"Srishti Sharma" <srishtishar@gmail.com>,
devel@driverdev.osuosl.org
Subject: Re: [PATCH 1/7] media: atomisp: stop producing hundreds of kernel-doc warnings
Date: Wed, 29 Nov 2017 10:28:26 -0200 [thread overview]
Message-ID: <20171129102826.12c46e21@recife.lan> (raw)
In-Reply-To: <20171129102457.4b41091c@recife.lan>
Em Wed, 29 Nov 2017 10:24:57 -0200
Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:
> Em Wed, 29 Nov 2017 14:14:54 +0200
> Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
>
> > Hi Mauro,
> >
> > Thanks for the patch.
> >
> > On Wed, Nov 29, 2017 at 07:08:04AM -0500, Mauro Carvalho Chehab wrote:
> > > A recent change on Kernel 4.15-rc1 causes all tags with
> > > /** to be handled as kernel-doc markups. Well, several
> > > atomisp modules, it doesn't use kernel-doc, but some other
> > > documentation markup (doxygen?).
> > >
> > > So, suppress all those warns by replacing /** by /*.
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> >
> > I presume you haven't written the patch manually. There are other changes
> > that described by the comment, too, such as removing lesser
> > than-characaters.
> >
> > It'd be good to mention how it's been generated.
>
> Yeah, I used a simple script, and manually fixed a few minor things
> that were still causing warnings.
>
> The core changes were done via:
>
> for i in $(find drivers/staging/media/atomisp -type f); do sed 's,/\*\* ,/\*, ' -i $i; done
> for i in $(find drivers/staging/media/atomisp -type f); do sed 's,/\*\*<,/\**,' -i $i; done
> for i in drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/debug/src/ia_css_debug.c drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css_sp.c drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/rmgr/src/rmgr_vbuf.c; do perl -ne 's,\/\*\*$,/*,g; print $_' $i > a && mv a $i; done;
>
> I'll add it at the patch description.
>
> Thanks,
> Mauro
Changed patch description to the one enclosed.
commit 699a8caa3de69b2bdaa54b9347c29644bc2222a6
Author: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Date: Wed Nov 29 03:16:17 2017 -0500
media: atomisp: stop producing hundreds of kernel-doc warnings
A recent change on Kernel 4.15-rc1 causes all tags with
/** to be handled as kernel-doc markups. Well, several
atomisp modules, it doesn't use kernel-doc, but some other
documentation markup (doxygen?).
So, suppress all those warns by:
- replacing /**< by /**.
- replacing /** by /*.
The core changes were done with:
for i in $(find drivers/staging/media/atomisp -type f); do sed 's,/\*\* ,/\*, ' -i $i; done
for i in $(find drivers/staging/media/atomisp -type f); do sed 's,/\*\*<,/\**,' -i $i; done
for i in drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/debug/src/ia_css_debug.c drivers/staging/media/atomisp/pci/atomisp2/css2400/sh_css_sp.c drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/rmgr/src/rmgr_vbuf.c; do perl -ne 's,\/\*\*$,/*,g; print $_' $i > a && mv a $i; done;
A few manual adjustments were made, where needed.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Thanks,
Mauro
next prev parent reply other threads:[~2017-11-29 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c73fcbc4af259923feac19eda4bb5e996b6de0fd.1511952403.git.mchehab@s-opensource.com>
2017-11-29 12:08 ` [PATCH 2/7] media: rc: fix kernel-doc parameter names Mauro Carvalho Chehab
2017-11-29 12:08 ` [PATCH 3/7] media: v4l2-core: Fix kernel-doc markups Mauro Carvalho Chehab
2017-11-29 12:08 ` [PATCH 4/7] media: davinci: fix kernel-doc warnings Mauro Carvalho Chehab
2017-11-30 19:58 ` Lad, Prabhakar
2017-11-29 12:08 ` [PATCH 5/7] media: venc: don't use kernel-doc for undescribed enums Mauro Carvalho Chehab
2017-11-29 12:08 ` [PATCH 6/7] media: exynos4-is: fix kernel-doc warnings Mauro Carvalho Chehab
2017-11-29 12:08 ` [PATCH 7/7] media: m5mols: fix some kernel-doc markups Mauro Carvalho Chehab
2017-11-29 12:14 ` [PATCH 1/7] media: atomisp: stop producing hundreds of kernel-doc warnings Sakari Ailus
2017-11-29 12:24 ` Mauro Carvalho Chehab
2017-11-29 12:28 ` Mauro Carvalho Chehab [this message]
2017-11-29 12:34 ` Sakari Ailus
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=20171129102826.12c46e21@recife.lan \
--to=mchehab@s-opensource.com \
--cc=alan@linux.intel.com \
--cc=amitoj1606@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=arushisinghal19971997@gmail.com \
--cc=colin.king@canonical.com \
--cc=daeseok.youn@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=geliangtang@gmail.com \
--cc=georgiana.chelu93@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gurooodas@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=hdegoede@redhat.com \
--cc=jeremy.lefaure@lse.epita.fr \
--cc=joe@perches.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=melko@frugalware.org \
--cc=rvarsha016@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=singhalsimran0@gmail.com \
--cc=smklearn@gmail.com \
--cc=srishtishar@gmail.com \
--cc=thomas@m3y3r.de \
/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