public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Adrien Descamps <adrien.descamps@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Staging: wlan-ng: Fix sparse warnings by using appropriate endian types
Date: Thu, 9 Mar 2017 19:05:48 +0100	[thread overview]
Message-ID: <20170309180548.GA4557@kroah.com> (raw)
In-Reply-To: <1488567511-3284-1-git-send-email-adrien.descamps@gmail.com>

On Fri, Mar 03, 2017 at 07:58:30PM +0100, Adrien Descamps wrote:
> Fix some sparse warning by using correct endian types in structs and
> local variables.
> This patch only fix sparse warnings and do not change the logic.
> 
> Signed-off-by: Adrien Descamps <adrien.descamps@gmail.com>
> ---
> Compile tested only
>  drivers/staging/wlan-ng/hfa384x.h     | 58 +++++++++++++++++------------------
>  drivers/staging/wlan-ng/hfa384x_usb.c |  2 +-
>  drivers/staging/wlan-ng/p80211conv.h  | 28 ++++++++---------
>  3 files changed, 44 insertions(+), 44 deletions(-)

Patch does not apply to my staging-next branch.  Can you rebase it and
resend?

thanks,

greg k-h

  parent reply	other threads:[~2017-03-09 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 20:30 [PATCH 1/2] Fix sparse warnings by using appropriate endian types Adrien Descamps
2017-03-02 20:30 ` [PATCH 2/2] Fix endiannes error Adrien Descamps
2017-03-03 11:29   ` Dan Carpenter
2017-03-03 18:58     ` [PATCH 1/2] Staging: wlan-ng: Fix sparse warnings by using appropriate endian types Adrien Descamps
2017-03-03 18:58       ` [PATCH 2/2] Staging: wlan-ng: Fix endian error Adrien Descamps
2017-03-09 18:05       ` Greg KH [this message]
2017-03-09 20:15         ` [PATCH 1/2] Staging: wlan-ng: Fix sparse warnings by using appropriate endian types Adrien Descamps
2017-03-09 20:15           ` [PATCH 2/2] Staging: wlan-ng: Fix endian error Adrien Descamps

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=20170309180548.GA4557@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adrien.descamps@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --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