public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marcos Paulo de Souza <marcos.mage@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	devel@driverdev.osuosl.org, Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] staging: vt6655: card.c, srom.c, vntwifi.c: Code cleanup
Date: Thu, 8 Dec 2011 11:25:33 -0800	[thread overview]
Message-ID: <20111208192533.GA19310@kroah.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1112042000070.5963@cactuar.localhost>

On Sun, Dec 04, 2011 at 08:01:39PM -0200, Marcos Paulo de Souza wrote:
> On Sat, 3 Dec 2011, Dan Carpenter wrote:
> >On Fri, Dec 02, 2011 at 07:58:12PM +0000, Marcos Paulo de Souza wrote:
> >>This patch removes commented code, useless comments, blank lines and fix
> >>coding style of the headers of functions.
> >>
> >>Signed-off-by: Marcos Paulo de Souza <marcos.mage@gmail.com>
> >>Cc: Greg Kroah-Hartman <gregkh@suse.de>
> >>Cc: devel@driverdev.osuosl.org
> >>---
> >> /*
> >>- * Description: Test if bits off in eeprom
> >>- *
> >>- * Parameters:
> >>- *  In:
> >>- *      dwIoBase        - I/O base address
> >>- *      byContntOffset  - address of EEPROM
> >>- *      byTestBits      - bits to test
> >>- *  Out:
> >>- *      none
> >>- *
> >>- * Return Value: true if all test bits off; otherwise false
> >>- *
> >>+ * Test if bits off in eeprom
> >>  */
> >
> >Some of these seems sort of useful.  It might be better to change
> >them to doc-book format instead of deleting them:
> >
> >/**
> >* SROMbIsRegBitsOff() - Test if bits off in eeprom
> >* @dwIoBase:       I/O base address
> >* @byContntOffset: Address of EEPROM
> >* @byTestBits:     Bits to test
> >*
> >* Returns true if all test bits off; otherwise false.
> >*/
> >
> >There is a howto in Documentation/kernel-doc-nano-HOWTO.txt.
> 
> Thanks for the suggestion Dan. I will do it for these 3 patches.
> 
> Greg, please delte this patches, I will sent them again.

Ugh, "which" patches are you referring to?

I see lots here from you, with different back-and-forth from Dan, and I
don't really see an easy way to tell which thread from which, given that
you didn't thread the patches using git-send-email.

So, I've dropped all patches from you from my patch queue, can you
please resend the ones that I am supposed to apply that have been
reviewed by Dan as being acceptable?

thanks,

greg k-h

      reply	other threads:[~2011-12-08 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 19:58 [PATCH 3/3] staging: vt6655: card.c, srom.c, vntwifi.c: Code cleanup Marcos Paulo de Souza
2011-12-03  8:32 ` Dan Carpenter
2011-12-04 22:01   ` Marcos Paulo de Souza
2011-12-08 19:25     ` Greg KH [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=20111208192533.GA19310@kroah.com \
    --to=greg@kroah.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcos.mage@gmail.com \
    /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