From: David Roddick <dgroddick@gmail.com>
To: gregkh@linuxfoundation.org
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
David Roddick <dgroddick@gmail.com>
Subject: [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 18:52:28 +1100 [thread overview]
Message-ID: <1393228348-13747-1-git-send-email-dgroddick@gmail.com> (raw)
Signed-off-by: David Roddick <dgroddick@gmail.com>
---
drivers/staging/comedi/drivers/poc.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/comedi/drivers/poc.c b/drivers/staging/comedi/drivers/poc.c
index 2ae4ee1..22c7392 100644
--- a/drivers/staging/comedi/drivers/poc.c
+++ b/drivers/staging/comedi/drivers/poc.c
@@ -36,15 +36,15 @@ Configuration options:
struct boarddef_struct {
const char *name;
unsigned int iosize;
- int (*setup) (struct comedi_device *);
+ int (*setup)(struct comedi_device *);
int type;
int n_chan;
int n_bits;
- int (*winsn) (struct comedi_device *, struct comedi_subdevice *,
+ int (*winsn)(struct comedi_device *, struct comedi_subdevice *,
struct comedi_insn *, unsigned int *);
- int (*rinsn) (struct comedi_device *, struct comedi_subdevice *,
+ int (*rinsn)(struct comedi_device *, struct comedi_subdevice *,
struct comedi_insn *, unsigned int *);
- int (*insnbits) (struct comedi_device *, struct comedi_subdevice *,
+ int (*insnbits)(struct comedi_device *, struct comedi_subdevice *,
struct comedi_insn *, unsigned int *);
const struct comedi_lrange *range;
};
--
1.8.5.3
next reply other threads:[~2014-02-24 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 7:52 David Roddick [this message]
2014-02-24 8:10 ` [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 Dan Carpenter
-- 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=1393228348-13747-1-git-send-email-dgroddick@gmail.com \
--to=dgroddick@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--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 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.