public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Borg <cyborg101010@gmail.com>
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
	dan.carpenter@oracle.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: das1800: Fixing foo * bar should be foo *bar
Date: Mon, 13 Jan 2014 15:52:05 -0800	[thread overview]
Message-ID: <20140113235205.GA22441@kroah.com> (raw)
In-Reply-To: <1389655155-20071-1-git-send-email-cyborg101010@gmail.com>

On Mon, Jan 13, 2014 at 11:19:15PM +0000, Joe Borg wrote:
> Fixed an error flagged by checkpatch.pl, 'foo * bar should be foo
> *bar' in the parameters of function munge_data().
> 
> Signed-off-by: Joe Borg <cyborg101010@gmail.com>
> ---
>  drivers/staging/comedi/drivers/das1800.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/comedi/drivers/das1800.c b/drivers/staging/comedi/drivers/das1800.c
> index 1880038..8fb87df 100644
> --- a/drivers/staging/comedi/drivers/das1800.c
> +++ b/drivers/staging/comedi/drivers/das1800.c
> @@ -462,7 +462,7 @@ static inline uint16_t munge_bipolar_sample(const struct comedi_device *dev,
>  	return sample;
>  }
>  
> -static void munge_data(struct comedi_device *dev, uint16_t * array,
> +static void munge_data(struct comedi_device *dev, uint16_t *array,
>  		       unsigned int num_elements)

Ok, after all that work, it turns out I can't even apply this patch as
someone else did it already a while ago.  You should be working off of
linux-next, or my staging.git tree, not Linus's tree, as that does not
contain all of the work we are doing on the next version of linux (hence
the -next).

So, care to try again with a different fix?

thanks,

greg k-h

      parent reply	other threads:[~2014-01-13 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 23:19 [PATCH] DAS1800: Fixing foo * bar should be foo *bar Joe Borg
2014-01-13 23:50 ` Greg KH
2014-01-13 23:52 ` 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=20140113235205.GA22441@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=cyborg101010@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hsweeten@visionengravers.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