From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Kacper Kołodziej" <kacper@kolodziej.it>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
Michael Straube <straube.linux@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
Janani Sankara Babu <jananis37@gmail.com>
Subject: Re: [PATCH] staging: rtl8188eu: break line longer than 80 cols
Date: Thu, 12 Jul 2018 08:17:01 +0200 [thread overview]
Message-ID: <20180712061701.GF20905@kroah.com> (raw)
In-Reply-To: <20180711192411.24817-1-kacper@kolodziej.it>
On Wed, Jul 11, 2018 at 09:24:09PM +0200, Kacper Kołodziej wrote:
> Signed-off-by: Kacper Kołodziej <kacper@kolodziej.it>
Sorry, but I need a changelog text in order to be able to take a patch.
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-12 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 19:24 [PATCH] staging: rtl8188eu: break line longer than 80 cols Kacper Kołodziej
2018-07-12 6:17 ` Greg Kroah-Hartman [this message]
2018-07-12 8:11 ` Kacper Kołodziej
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=20180712061701.GF20905@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=hdegoede@redhat.com \
--cc=jananis37@gmail.com \
--cc=kacper@kolodziej.it \
--cc=linux-kernel@vger.kernel.org \
--cc=straube.linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox