From: Dan Carpenter <dan.carpenter@oracle.com>
To: menna_tarek <mennatallah.dawood@gmail.com>
Cc: devel@driverdev.osuosl.org, lidza.louina@gmail.com,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH] staging: dgnc: Fixing a warning of line over 80 characters
Date: Wed, 21 Jan 2015 13:51:59 +0300 [thread overview]
Message-ID: <20150121105159.GI6456@mwanda> (raw)
In-Reply-To: <20150121104659.GA7490@Menna-HP>
On Wed, Jan 21, 2015 at 12:46:59PM +0200, menna_tarek wrote:
> This patch fixes the following checkpatch.pl warning:
> WARNING: line over 80 characters
>
> Signed-off-by: menna_tarek <mennatallah.dawood@gmail.com>
These are supposed to be your actual name that you use to sign legal
documents with correct capitalization etc. Same for the From header.
regards,
dan carpenter
prev parent reply other threads:[~2015-01-21 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 10:46 [PATCH] staging: dgnc: Fixing a warning of line over 80 characters menna_tarek
2015-01-21 10:51 ` Dan Carpenter [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=20150121105159.GI6456@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mennatallah.dawood@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