From: Greg KH <gregkh@linuxfoundation.org>
To: Mikulas Tomanka <mklstmnk@gmail.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
linux-fbdev@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: deleted couple of blank lines at the very end
Date: Sat, 04 Jun 2016 16:42:32 +0000 [thread overview]
Message-ID: <20160604164232.GA7463@kroah.com> (raw)
In-Reply-To: <20160604104218.18806-1-mklstmnk@gmail.com>
On Sat, Jun 04, 2016 at 10:42:18AM +0000, Mikulas Tomanka wrote:
> Signed-off-by: Mikulas Tomanka <mklstmnk@gmail.com>
I can't take patches without a changelog text, sorry.
prev parent reply other threads:[~2016-06-04 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 8:43 [PATCH] staging: sm750fb: deleted couple of blank lines at the very end Mikulas Tomanka
2016-06-04 16:42 ` Greg KH [this message]
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=20160604164232.GA7463@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mklstmnk@gmail.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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 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).