All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Namrata A Shettar <namrataashettar@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
	Rithvik Patibandla <rithvikp98@gmail.com>,
	outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH 2/2] staging: vt6656: Make return type changes of functions
Date: Tue, 27 Sep 2016 13:09:30 +0200	[thread overview]
Message-ID: <20160927110930.GA16803@kroah.com> (raw)
In-Reply-To: <9a6403af18f7bd45499f6745ab61d6dd4aa7dea2.1474912143.git.namrataashettar@gmail.com>

On Mon, Sep 26, 2016 at 11:56:10PM +0530, Namrata A Shettar wrote:
> Change return type of functions to reflect changes in code.
> 
> Signed-off-by: Namrata A Shettar <namrataashettar@gmail.com>
> ---
>  drivers/staging/vt6656/card.h | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/vt6656/card.h b/drivers/staging/vt6656/card.h
> index c2cde7e..84270c1 100644
> --- a/drivers/staging/vt6656/card.h
> +++ b/drivers/staging/vt6656/card.h
> @@ -41,14 +41,14 @@ void vnt_update_ifs(struct vnt_private *);
>  void vnt_update_top_rates(struct vnt_private *);
>  int vnt_ofdm_min_rate(struct vnt_private *);
>  void vnt_adjust_tsf(struct vnt_private *, u8, u64, u64);
> -bool vnt_get_current_tsf(struct vnt_private *, u64 *);
> +void vnt_get_current_tsf(struct vnt_private *, u64 *);
>  bool vnt_clear_current_tsf(struct vnt_private *);
>  void vnt_reset_next_tbtt(struct vnt_private *, u16);
>  void vnt_update_next_tbtt(struct vnt_private *, u64, u16);
>  u64 vnt_get_next_tbtt(u64, u16);
>  u64 vnt_get_tsf_offset(u8 byRxRate, u64 qwTSF1, u64 qwTSF2);
> -int vnt_radio_power_off(struct vnt_private *);
> -int vnt_radio_power_on(struct vnt_private *);
> +void vnt_radio_power_off(struct vnt_private *);
> +void vnt_radio_power_on(struct vnt_private *);
>  u8 vnt_get_pkt_type(struct vnt_private *);
>  void vnt_set_bss_mode(struct vnt_private *);

You have to do this in your first patch, as the build broke without
these changes, right?

You can never break the build with any single patch.

Please fix up and resend.

thanks,

greg k-h


  reply	other threads:[~2016-09-27 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 18:25 [PATCH 0/2] staging: vt6656: Fix return values Namrata A Shettar
2016-09-26 18:25 ` [PATCH 1/2] staging: vt6656: Remove unnecessary " Namrata A Shettar
2016-09-26 18:26 ` [PATCH 2/2] staging: vt6656: Make return type changes of functions Namrata A Shettar
2016-09-27 11:09   ` Greg Kroah-Hartman [this message]
2016-09-27 16:39     ` Namrata A Shettar
2016-09-28  9:24       ` Greg Kroah-Hartman

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=20160927110930.GA16803@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=forest@alittletooquiet.net \
    --cc=namrataashettar@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=rithvikp98@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 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.