All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jake Champlin <jake.champlin.27@gmail.com>
Cc: abbotti@mev.co.uk, devel@driverdev.osuosl.org,
	fmhess@users.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: Comedi: amplc_dio200: Fixed Bracing Issue
Date: Tue, 29 Jan 2013 23:04:30 -0500	[thread overview]
Message-ID: <20130130040430.GA17683@kroah.com> (raw)
In-Reply-To: <20130125185404.GA7672@gmail.com>

On Fri, Jan 25, 2013 at 01:54:08PM -0500, Jake Champlin wrote:
> Fixed Bracing Issue flagged by checkpatch.pl
> 
> Signed-off-by: Jake Champlin <jake.champlin.27@gmail.com>
> ---
>  drivers/staging/comedi/drivers/amplc_dio200.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/comedi/drivers/amplc_dio200.c b/drivers/staging/comedi/drivers/amplc_dio200.c
> index 5f309ba..b09269d 100644
> --- a/drivers/staging/comedi/drivers/amplc_dio200.c
> +++ b/drivers/staging/comedi/drivers/amplc_dio200.c
> @@ -1977,8 +1977,7 @@ static int dio200_auto_attach(struct comedi_device *dev,
>  		devpriv->io.u.iobase = (unsigned long)base;
>  		devpriv->io.regtype = io_regtype;
>  	}
> -	switch (thisboard->model)
> -	{
> +	switch (thisboard->model) {
>  	case pcie215_model:
>  	case pcie236_model:
>  	case pcie296_model:

Why did you send me the same patch twice here?  You sent this back on
January 18th, and I already applied it to the tree, didn't you get an
email telling you so?

greg k-h

  reply	other threads:[~2013-01-30  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 18:54 [PATCH] Staging: Comedi: amplc_dio200: Fixed Bracing Issue Jake Champlin
2013-01-30  4:04 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-19  1:23 [PATCH] Staging: Comedi: amplc_dio200: Fixed bracing issue Jake Champlin
2013-01-19  1:21 Jake Champlin

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=20130130040430.GA17683@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=jake.champlin.27@gmail.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.