From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Solving checkpatch error with lex
Date: Wed, 17 Dec 2014 20:07:53 +0100 [thread overview]
Message-ID: <1418843273.2123.29.camel@x220> (raw)
In-Reply-To: <5491CCC8.4050409@gmail.com>
On Thu, 2014-12-18 at 00:04 +0530, karthik nayak wrote:
> was trying to fix the checkpatch error of not using c99 comments in the
> file
> drivers/staging/rtl8192u/r8192U_dm.c
> so I wrote a lex program to do so since there were way too many to do it
> manually.
> Could anyone have a look at my lex code and tell me if I need to change it.
> I have attached the lex code.
> As per my testing it works perfectly, would love a second opinion.
I see no reason to review someone's lex code. I guess very few people
are actually willing to do that.
Why don't you just send in the diff? Or even better, the patch you
intend to submit. Almost everybody here can read diffs or patches.
Hope this helps,
Paul Bolle
next prev parent reply other threads:[~2014-12-17 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 18:34 Solving checkpatch error with lex karthik nayak
2014-12-17 18:52 ` Valdis.Kletnieks at vt.edu
2014-12-17 19:07 ` Paul Bolle [this message]
2014-12-17 19:10 ` karthik nayak
2014-12-17 19:36 ` Greg KH
2014-12-17 21:24 ` Valdis.Kletnieks at vt.edu
2014-12-18 0:47 ` Greg KH
2014-12-18 6:07 ` karthik nayak
2014-12-17 19:11 ` Paul Bolle
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=1418843273.2123.29.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).