From: Sergei Shtylyov <sshtylyov@mvista.com>
To: navin patidar <navinp@cdac.in>
Cc: gregkh@linuxfoundation.org, mfm@muteddisk.com,
linux-usb@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: usbip: stub_dev: Fixed oops during removal of usbip_host
Date: Fri, 14 Sep 2012 18:16:07 +0400 [thread overview]
Message-ID: <50533C27.2040100@mvista.com> (raw)
In-Reply-To: <CAPV97yfV27x8hB2WUCVmGWEU7i21Y5K5trig2fzQBx+VB_Yk2g@mail.gmail.com>
Hello.
On 09/14/2012 04:36 PM, navin patidar wrote:
> hi Sergei,
> checkpatch.pl <http://checkpatch.pl> didn't complain any thing about patch
> coding style.
checkpatch.pl only complains about // comments, IIRC. But see
Documentation/CodingStyle chapter 8 about multi-line comments. As for adding
spaces, it's more for aesthetic reasons...
> Anyway thanks for reviewing the patch.
> i will send this patch again with corrections.
Thanks you.
> --navin-patidar
WBR, Sergei
next prev parent reply other threads:[~2012-09-14 14:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 9:53 [PATCH] staging: usbip: stub_dev: Fixed oops during removal of usbip_host navin patidar
2012-09-14 11:42 ` Sergei Shtylyov
2012-09-14 12:04 ` Sebastian Andrzej Siewior
2012-09-14 14:29 ` navin patidar
[not found] ` <CAPV97yfV27x8hB2WUCVmGWEU7i21Y5K5trig2fzQBx+VB_Yk2g@mail.gmail.com>
2012-09-14 14:16 ` Sergei Shtylyov [this message]
2012-09-17 12:19 ` Greg KH
2012-09-14 13:21 navin patidar
2012-09-14 14:16 ` Dan Carpenter
2012-09-14 14:28 ` Sebastian Andrzej Siewior
2012-09-14 14:41 ` Dan Carpenter
2012-09-18 4:00 navin patidar
2012-09-18 7:40 ` Dan Carpenter
2012-09-18 9:32 ` navin patidar
2012-09-18 9:36 ` Dan Carpenter
2012-09-18 11:44 ` navin patidar
2012-09-18 13:15 ` Dan Carpenter
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=50533C27.2040100@mvista.com \
--to=sshtylyov@mvista.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mfm@muteddisk.com \
--cc=navinp@cdac.in \
/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).