From: Greg KH <gregkh@linuxfoundation.org>
To: Ajay Singh <ajay.kathat@microchip.com>
Cc: devel@driverdev.osuosl.org, venkateswara.kaja@microchip.com,
linux-wireless@vger.kernel.org, ganesh.krishna@microchip.com,
adham.abozaeid@microchip.com, aditya.shankar@microchip.com,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH 00/11] staging: wilc1000: fix for checkpatch and handled malloc memory properly
Date: Mon, 23 Apr 2018 15:43:33 +0200 [thread overview]
Message-ID: <20180423134333.GA21978@kroah.com> (raw)
In-Reply-To: <20180404104525.22abe3fc@ajaysk-VirtualBox>
On Wed, Apr 04, 2018 at 10:45:25AM +0530, Ajay Singh wrote:
> Hi Greg,
>
> On Wed, 28 Mar 2018 13:31:01 +0200
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > On Tue, Mar 27, 2018 at 12:52:13PM +0530, Ajay Singh wrote:
> > >
> > > Please let me know, in case I have to rework and resubmit this
> > > patch series to make them into staging branch.
> >
> > You already sent a v2 series for this, right? Why respond to the v1
> > set?
> >
>
> Sorry for late reply.
>
> V2 series was not sent for this patchset. No code updates were
> submitted for this patch series. It's an independent patch series
> with 11 patches and had changes different from other patch series.
>
> Just for information, the v2 patch series was submitted for different
> patch series which had 9 patches.
>
> Please let me know if any other information/action is required from
> my side to include this patch series to staging.
THis patch series is long gone from my queue. Please resend it if I
have not applied it.
greg k-h
prev parent reply other threads:[~2018-04-23 13:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 16:55 [PATCH 00/11] staging: wilc1000: fix for checkpatch and handled malloc memory properly Ajay Singh
2018-03-20 16:55 ` [PATCH 01/11] staging: wilc1000: refactor scan() to free kmalloc memory on failure cases Ajay Singh
2018-03-20 19:46 ` Dan Carpenter
2018-03-21 5:05 ` Ajay Singh
2018-03-20 16:55 ` [PATCH 02/11] staging: wilc1000: removed unused global variables for gtk and ptk information Ajay Singh
2018-03-20 16:55 ` [PATCH 03/11] staging: wilc1000: remove line over 80 char warnings in set_wiphy_params() Ajay Singh
2018-03-20 16:55 ` [PATCH 04/11] staging: wilc1000: refactor WILC_WFI_p2p_rx() to avoid line over 80 char Ajay Singh
2018-03-21 7:13 ` Dan Carpenter
2018-03-21 13:55 ` Claudiu Beznea
2018-03-20 16:55 ` [PATCH 05/11] staging: wilc1000: rename WILC_WFI_p2p_rx & s32Freq to avoid camelCase Ajay Singh
2018-03-20 16:55 ` [PATCH 06/11] staging: wilc1000: refactor mgmt_tx to fix line over 80 chars Ajay Singh
2018-03-21 7:40 ` Dan Carpenter
2018-03-21 13:59 ` Claudiu Beznea
2018-03-20 16:55 ` [PATCH 07/11] staging: wilc1000: rename hAgingTimer to avoid camelCase issue Ajay Singh
2018-03-20 16:55 ` [PATCH 08/11] staging: wilc1000: fix line over 80 char issue in clear_shadow_scan() Ajay Singh
2018-03-20 16:55 ` [PATCH 09/11] staging: wilc1000: remove line over 80 char in cfg_connect_result() Ajay Singh
2018-03-21 7:49 ` Dan Carpenter
2018-03-20 16:55 ` [PATCH 10/11] staging: wilc1000: remove unused 'struct add_key_params' Ajay Singh
2018-03-20 16:55 ` [PATCH 11/11] staging: wilc1000: remove line over 80 char warning in few functions Ajay Singh
2018-03-21 7:51 ` [PATCH 00/11] staging: wilc1000: fix for checkpatch and handled malloc memory properly Dan Carpenter
2018-03-21 9:20 ` Ajay Singh
2018-03-21 14:04 ` Claudiu Beznea
2018-03-27 7:22 ` Ajay Singh
2018-03-27 8:55 ` Claudiu Beznea
2018-03-27 13:16 ` Ajay Singh
2018-03-28 11:31 ` Greg KH
2018-04-04 5:15 ` Ajay Singh
2018-04-23 13:43 ` 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=20180423134333.GA21978@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adham.abozaeid@microchip.com \
--cc=aditya.shankar@microchip.com \
--cc=ajay.kathat@microchip.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=linux-wireless@vger.kernel.org \
--cc=venkateswara.kaja@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).