From: Greg KH <gregkh@linuxfoundation.org>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/9] staging: rtl8192u: Fixing coding style issues
Date: Thu, 16 Feb 2017 10:32:18 -0800 [thread overview]
Message-ID: <20170216183218.GB5188@kroah.com> (raw)
In-Reply-To: <CALrZqyPyJ9Z5N91G073hAEr=YTD5BvRUVCikbBh1kxXiq5dx+g@mail.gmail.com>
On Wed, Feb 15, 2017 at 01:48:13PM +0530, SIMRAN SINGHAL wrote:
> On Wed, Feb 15, 2017 at 9:01 AM, Joe Perches <joe@perches.com> wrote:
> > On Wed, 2017-02-15 at 08:52 +0530, SIMRAN SINGHAL wrote:
> >> Yes, I totally agree with joe.
> >>
> >> But as there is no coding style issue in this patch.
> >
> > Style is more than just checkpatch conformity.
> >
> >> So, do I have to resend the complete patch series again?
> >
> > I'm not applying any of these so that's entirely up
> > to Greg.
> >
> > Perhaps he might apply the first 5 patches and reject
> > this one, maybe he might apply all the patches.
> >
> > In any case, do strive to develop some reasonable
> > semblance of style and do more than just checkpatch
> > suggested patches and find and fix some actual defect
> > somewhere.
>
> Joe, I am new to Linux kernel and just have basic knowledge of
> C and C++.
As Joe said, the kernel is _not_ the project to learn C with. Please
get some more experience with userspace programs in C first, before
working on the kernel. It will be much easier for you.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-16 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 20:14 [PATCH v2 6/9] staging: rtl8192u: Fixing coding style issues simran singhal
2017-02-14 20:23 ` Joe Perches
2017-02-15 3:22 ` SIMRAN SINGHAL
2017-02-15 3:31 ` Joe Perches
2017-02-15 8:18 ` SIMRAN SINGHAL
2017-02-15 9:23 ` Joe Perches
2017-02-16 18:32 ` Greg KH [this message]
2017-02-16 19:08 ` SIMRAN SINGHAL
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=20170216183218.GB5188@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=singhalsimran0@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.