The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Hartley Sweeten <HartleyS@visionengravers.com>
Cc: Fred Akers <knivey@botops.net>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"abbotti@mev.co.uk" <abbotti@mev.co.uk>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Staging: comedi: addi-data: Fix long CamelCase function names
Date: Tue, 11 Mar 2014 10:49:12 -0700	[thread overview]
Message-ID: <1394560152.20021.3.camel@joe-AO722> (raw)
In-Reply-To: <DC148C5AA1CEBA4E87973D432B1C2D8825DAD0AF@P3PWEX4MB008.ex4.secureserver.net>

On Tue, 2014-03-11 at 17:42 +0000, Hartley Sweeten wrote:
> On Tuesday, March 11, 2014 10:33 AM, Fred Akers wrote:
> > This patch fixes a few function names that are very long and are
> > not in the correct naming style
[]
> > diff --git a/drivers/staging/comedi/drivers/addi-data/hwdrv_apci035.c b/drivers/staging/comedi/drivers/addi-data/hwdrv_apci035.c
[]
> > @@ -111,7 +111,7 @@ static int i_Temp;
> >  static int i_Flag = 1;
> >  /*
> >  +----------------------------------------------------------------------------+
> > -| Function   Name   : int i_APCI035_ConfigTimerWatchdog                      |
> > +| Function   Name   : int apci035_timer_config                      |
> >  |			  (struct comedi_device *dev,struct comedi_subdevice *s,               |
> >  |                      struct comedi_insn *insn,unsigned int *data)                     |
> >  +----------------------------------------------------------------------------+
> 
> Nitpick... These obvious function comment blocks should be removed.
> That should be a separate patch. Maybe a patch 1/2 before this one so
> you don't have to update the comments.

Maybe convert them to kernel-doc style?

/**
 * foobar() - short function description of foobar
 * @arg1:	Describe the first argument to foobar.
 * @arg2:	Describe the second argument to foobar.
 *		One can provide multiple line descriptions
 *		for arguments.



  reply	other threads:[~2014-03-11 17:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09  7:26 [PATCH] Staging: comedi: apci_1564: Fix long CamelCase function names Fred Akers
2014-03-11 14:31 ` Ian Abbott
2014-03-11 15:01   ` Fred Akers
2014-03-11 17:32 ` [PATCH v2] Staging: comedi: addi-data: " Fred Akers
2014-03-11 17:42   ` Hartley Sweeten
2014-03-11 17:49     ` Joe Perches [this message]
2014-03-11 17:53       ` Hartley Sweeten
2014-03-11 22:19 ` [PATCH v3 1/2] " Fred Akers
2014-03-12  0:07   ` Hartley Sweeten
2014-03-12  1:06   ` Hartley Sweeten
2014-03-12  1:25     ` Fred Akers
2014-03-12 17:48     ` Ian Abbott
2014-03-11 22:19 ` [PATCH v3 2/2] Staging: Comedi: addi-data: Clean up function comments Fred Akers

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=1394560152.20021.3.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=HartleyS@visionengravers.com \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=knivey@botops.net \
    --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