From: Kroah-Hartman <gregkh@linuxfoundation.org>
To: Patard <arnaud.patard@rtp-net.org>,
yuzibode@126.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: xgifb: vgatypes.h: Coding style warning fix for block comments
Date: Sun, 7 Feb 2016 20:14:36 -0800 [thread overview]
Message-ID: <20160208041436.GA17635@kroah.com> (raw)
In-Reply-To: <20160115092958.GA9097@debian>
On Fri, Jan 15, 2016 at 05:30:02PM +0800, YU Bo wrote:
> This patch is to vgatypes.h file that fixes up following warnings
> reported by checkpatch.pl tool
>
> Signed-off-by: YU Bo <tsu.yubo@gmail.com>
> ---
> drivers/staging/xgifb/vgatypes.h | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
None of your patches applied, are you sure you are sending them
properly?
next prev parent reply other threads:[~2016-02-08 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 9:30 [PATCH] Staging: xgifb: vgatypes.h: Coding style warning fix for block comments YU Bo
2016-02-08 4:14 ` Kroah-Hartman [this message]
2016-02-15 12:18 ` Bo YU
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=20160208041436.GA17635@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnaud.patard@rtp-net.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuzibode@126.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