From: Greg KH <gregkh@linuxfoundation.org>
To: Ajay.Kathat@microchip.com
Cc: linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
johannes@sipsolutions.net, Adham.Abozaeid@microchip.com
Subject: Re: [PATCH] staging: wilc1000: refactor p2p action frames handling API's
Date: Wed, 12 Feb 2020 13:47:40 -0800 [thread overview]
Message-ID: <20200212214740.GA2312757@kroah.com> (raw)
In-Reply-To: <20200212154503.8835-1-ajay.kathat@microchip.com>
On Wed, Feb 12, 2020 at 10:14:15AM +0000, Ajay.Kathat@microchip.com wrote:
> From: Ajay Singh <ajay.kathat@microchip.com>
>
> Refactor handling of P2P specific action frames. Make use of 'struct' to
> handle the P2P frames instead of manipulating using 'buf' pointer.
>
> Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
> ---
> [resending this patch as it failed to apply earlier]
I had to export this and apply it by hand as the base64 stuff here
really confused git :(
odd...
greg k-h
prev parent reply other threads:[~2020-02-12 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 10:14 [PATCH] staging: wilc1000: refactor p2p action frames handling API's Ajay.Kathat
2020-02-12 21:47 ` 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=20200212214740.GA2312757@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Adham.Abozaeid@microchip.com \
--cc=Ajay.Kathat@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=johannes@sipsolutions.net \
--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.