All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Litzinger <jlitzingerdev@gmail.com>
Cc: aditya.shankar@microchip.com, ganesh.krishna@microchip.com,
	linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
	dan.carpenter@oracle.com
Subject: Re: [PATCH RFC] staging: wilc1000: Refactor handling of HT caps fields
Date: Fri, 28 Apr 2017 11:58:57 +0200	[thread overview]
Message-ID: <20170428095857.GA22700@kroah.com> (raw)
In-Reply-To: <20170426044625.20529-1-jlitzingerdev@gmail.com>

On Tue, Apr 25, 2017 at 10:46:25PM -0600, Jason Litzinger wrote:
> The patch with this RFC addresses the following sparse warnings: 

So are you going to resend this as a non-RFC patch so that I can apply
it?  :)

thanks,

greg k-h

  parent reply	other threads:[~2017-04-28  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  4:46 [PATCH RFC] staging: wilc1000: Refactor handling of HT caps fields Jason Litzinger
2017-04-26  4:54 ` Jason Litzinger
2017-04-26  5:24   ` Jason Litzinger
2017-04-26  8:27 ` Dan Carpenter
2017-04-28  9:58 ` Greg KH [this message]
2017-04-28 16:11   ` Jason Litzinger

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=20170428095857.GA22700@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aditya.shankar@microchip.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ganesh.krishna@microchip.com \
    --cc=jlitzingerdev@gmail.com \
    --cc=linux-wireless@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.