From: Greg KH <gregkh@linuxfoundation.org>
To: Gargi Sharma <gs051095@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v2 0/2] fix multiple coding style issues
Date: Sat, 17 Sep 2016 20:06:32 +0200 [thread overview]
Message-ID: <20160917180632.GA26747@kroah.com> (raw)
In-Reply-To: <cover.1474119676.git.gs051095@gmail.com>
On Sat, Sep 17, 2016 at 07:48:19PM +0530, Gargi Sharma wrote:
> Patch 1 fixes the issue detected by checkpatch. Patch 1 modifies
> multi-line comments to follow kernel coding style guide.
> Patch 2 uses kernel coding style guide for macros.
The subject line here is odd, it doesn't say where in the kernel your
patches are for. Next time can you fix that up? Don't worry about it
for these.
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-17 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 14:18 [PATCH v2 0/2] fix multiple coding style issues Gargi Sharma
2016-09-17 14:18 ` [PATCH v2 1/2] staging: wlan-ng: use kernel preferred block commenting style Gargi Sharma
2016-09-17 21:25 ` Greg KH
2016-09-17 14:18 ` [PATCH v2 2/2] staging: wlan-ng: change indentation for macros Gargi Sharma
2016-09-17 18:06 ` Greg KH [this message]
2016-09-17 18:12 ` [PATCH v2 0/2] fix multiple coding style issues Gargi Sharma
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=20160917180632.GA26747@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gs051095@gmail.com \
--cc=outreachy-kernel@googlegroups.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.