From: Greg KH <gregkh@linuxfoundation.org>
To: "Pranay Kr. Srivastava" <pranjas@gmail.com>
Cc: mpa@pengutronix.de, nbd-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] nbd: Fix checkpatch errors.
Date: Tue, 3 May 2016 11:16:47 -0700 [thread overview]
Message-ID: <20160503181647.GA7706@kroah.com> (raw)
In-Reply-To: <1462293507-5010-3-git-send-email-pranjas@gmail.com>
On Tue, May 03, 2016 at 07:38:27PM +0300, Pranay Kr. Srivastava wrote:
> Signed-off-by: Pranay Kr. Srivastava <pranjas@gmail.com>
You have to have a changelog text.
And try doing one-patch-per-checkpatch-warning-type.
That's all I will accept for drivers/staging/ files, but maybe the nbd.c
maintainer has different rules.
good luck!
greg k-h
next prev parent reply other threads:[~2016-05-03 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 16:38 [PATCH v2 0/2] nbd: fix might_sleep warning and checkpatch fixes Pranay Kr. Srivastava
2016-05-03 16:38 ` [PATCH v2 1/2] nbd: Fix might_sleep warning on xmit timeout Pranay Kr. Srivastava
2016-05-03 16:38 ` [PATCH v2 2/2] nbd: Fix checkpatch errors Pranay Kr. Srivastava
2016-05-03 18:16 ` Greg KH [this message]
2016-06-02 1:03 ` Pavel Machek
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=20160503181647.GA7706@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=nbd-general@lists.sourceforge.net \
--cc=pranjas@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.