From: Dan Carpenter <dan.carpenter@oracle.com>
To: David Roddick <dgroddick@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
abbotti@mev.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: Fix coding style issue in poc.c This is a patch to remove unneccessary space after function pointer name found with checkpatch.pl
Date: Mon, 24 Feb 2014 11:10:10 +0300 [thread overview]
Message-ID: <20140224081010.GD26722@mwanda> (raw)
In-Reply-To: <1393228348-13747-1-git-send-email-dgroddick@gmail.com>
Subject is still messed up. Send the email to yourself first and then
to the list until you figure it out. (hint add a blank line).
regards,
dan carpenter
next prev parent reply other threads:[~2014-02-24 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 7:52 [PATCH] Staging: comedi: Fix coding style issue in poc.c This is a patch to remove unneccessary space after function pointer name found with checkpatch.pl David Roddick
2014-02-24 8:10 ` Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-23 23:02 David Roddick
2014-02-23 23:01 David Roddick
2014-02-24 7:39 ` Dan Carpenter
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=20140224081010.GD26722@mwanda \
--to=dan.carpenter@oracle.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=dgroddick@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).