From: Dan Carpenter <dan.carpenter@oracle.com>
To: Ralph Mueck <linux-kernel@rmueck.de>
Cc: devel@driverdev.osuosl.org, lisa@xenapiadmin.com,
linux-kernel@i4.cs.fau.de, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org,
Matthias Oefelein <ma.oefelein@arcor.de>
Subject: Re: [PATCH] beeceem: checkpatch whitespace cleanups
Date: Thu, 19 Dec 2013 17:36:29 +0300 [thread overview]
Message-ID: <20131219143628.GI28413@mwanda> (raw)
In-Reply-To: <1387451594-23168-1-git-send-email-linux-kernel@rmueck.de>
On Thu, Dec 19, 2013 at 12:13:14PM +0100, Ralph Mueck wrote:
> This patch contains several whitespace cleanups for the beeceem driver that have been reported by checkpatch.
Too ambigous.
> Subsequent patches will fix other issues that checkpatch complains about and which still remain after applying this patch.
Leave this information out.
regards,
dan caprenter
prev parent reply other threads:[~2013-12-19 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 11:13 [PATCH] beeceem: checkpatch whitespace cleanups Ralph Mueck
2013-12-19 14:36 ` 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=20131219143628.GI28413@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@rmueck.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@xenapiadmin.com \
--cc=ma.oefelein@arcor.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.