public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Gordon Mitchell <gordon@dumgoyne.me.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: rtl8187se: Fixed coding style issues
Date: Tue, 23 Feb 2010 16:35:42 -0800	[thread overview]
Message-ID: <20100224003542.GA12138@kroah.com> (raw)
In-Reply-To: <4B772E67.1030805@dumgoyne.me.uk>

On Sat, Feb 13, 2010 at 10:57:43PM +0000, Gordon Mitchell wrote:
> 
> commit eaf625ed89a5bbf40ef1e2740f2de6b6ac322c01
> Author: Gordon Mitchell <gordon@dumgoyne.me.uk>
> Date:   Sat Feb 13 21:09:24 2010 +0000
> 
>     Staging: rtl8187se: Apply kernel coding styles to r8180_93cx6.c
>     This patch to r8180_93cx6.c corrects errors and warnings found
>     by checkpatch.pl
>     Signed-off-by: Gordon Mitchell <gordon@dumgoyne.me.uk>
> 
> diff --git a/drivers/staging/rtl8187se/r8180_93cx6.c b/drivers/staging/rtl8187se/r8180_93cx6.c
> index 7e4711f..2a29cff 100644
> --- a/drivers/staging/rtl8187se/r8180_93cx6.c
> +++ b/drivers/staging/rtl8187se/r8180_93cx6.c
> @@ -22,13 +22,13 @@
>  
>  void eprom_cs(struct net_device *dev, short bit)
>  {
> -       if(bit)
> +       if (bit)
>                 write_nic_byte(dev, EPROM_CMD,

Hm, the tabs got converted to spaces here.  Care to try resending this
again?

thanks,

greg k-h

  reply	other threads:[~2010-02-24  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-13 22:57 [PATCH] Staging: rtl8187se: Fixed coding style issues Gordon Mitchell
2010-02-24  0:35 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-03 23:40 Mladen Mijatov
2013-04-29  1:31 [PATCH] Staging: rtl8187se: fixed " Matt Kilgore
2013-05-12 15:33 ` Greg KH

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=20100224003542.GA12138@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gordon@dumgoyne.me.uk \
    --cc=gregkh@suse.de \
    --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