From: Greg KH <gregkh@linuxfoundation.org>
To: Robin Naundorf <r.naundorf@fh-muenster.de>
Cc: lidza.louina@gmail.com, markh@compro.net,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: dgnc: Fix line over 80 characters
Date: Sun, 21 Aug 2016 17:57:04 +0200 [thread overview]
Message-ID: <20160821155704.GA4628@kroah.com> (raw)
In-Reply-To: <1471442349-7752-1-git-send-email-r.naundorf@fh-muenster.de>
On Wed, Aug 17, 2016 at 03:59:09PM +0200, Robin Naundorf wrote:
> Fix 'line over 80 characters' checkpatch.pl
> warning
>
> Signed-off-by: Robin Naundorf <r.naundorf@fh-muenster.de>
> ---
> drivers/staging/dgnc/dgnc_driver.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Someone else sent this same patch just before you did, sorry :(
next parent reply other threads:[~2016-08-21 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1471442349-7752-1-git-send-email-r.naundorf@fh-muenster.de>
2016-08-21 15:57 ` Greg KH [this message]
2015-02-20 12:15 [PATCH] Staging: dgnc: Fix line over 80 characters Yeliz Taneroglu
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=20160821155704.GA4628@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=r.naundorf@fh-muenster.de \
/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.