public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Oczek <jeffoczek@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: tidspbridge: Fix function pointer spacing in struct definition
Date: Sat, 14 Jun 2014 09:09:25 -0400	[thread overview]
Message-ID: <20140614130925.GA14744@fofx> (raw)
In-Reply-To: <1402716700.2756.3.camel@joe-AO725>

On Fri, Jun 13, 2014 at 08:31:40PM -0700, Joe Perches wrote:
> On Fri, 2014-06-13 at 22:48 -0400, Jeff Oczek wrote:
> > -	 s32(*fread) (void *, size_t, size_t, void *);
> > -	 s32(*fseek) (void *, long, int);
> > -	 s32(*ftell) (void *);
> > -	 s32(*fclose) (void *);
> > -	void *(*fopen) (const char *, const char *);
> > +	 s32 (*fread)(void *, size_t, size_t, void *);
> > +	 s32 (*fseek)(void *, long, int);
> > +	 s32 (*ftell)(void *);
> > +	 s32 (*fclose)(void *);
> > +	void *(*fopen)(const char *, const char *);
> 
> Better would be to describe the arguments with
> variable names and align all the return values
> 
> 	void *(*fopen
> 
> 	s32 (*fread)(void *arg1, size_t val1, size_t val2, void *ptr1);
> 	s32 (*fseek)(void *ptr1, long arg2, int arg3);
> 	s32 (*ftell)(void * ptr);
> 	s32 (*fclose)(void *ptr);
> 	void *(*fopen)(const char *ptr1, const char *ptr2);
> 
> where arg, val, ptr are actually useful descriptors
> 

Thanks Joe.  I was just trying to stay in the scope of making a
really trivial coding style change for the sake of following the
submission process for the first time.  But I'll resend based on
your suggestion.

  reply	other threads:[~2014-06-14 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14  2:48 [PATCH 1/2] staging: tidspbridge: Fix pointer spacing Jeff Oczek
2014-06-14  2:48 ` [PATCH 2/2] staging: tidspbridge: Fix function pointer spacing in struct definition Jeff Oczek
2014-06-14  3:31   ` Joe Perches
2014-06-14 13:09     ` Jeff Oczek [this message]
2014-06-14 13:21 ` [PATCH v2 1/2] staging: tidspbridge: Add parameter names to function ptrs in struct dbll_attrs Jeff Oczek
2014-06-14 13:21   ` [PATCH v2 2/2] staging: tidspbridge: Fix whitespace for pointers in function headers Jeff Oczek

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=20140614130925.GA14744@fofx \
    --to=jeffoczek@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox