Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from esa1.microchip.iphmx.com ([68.232.147.91]:42721 "EHLO
        esa1.microchip.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726046AbeHPJ6Z (ORCPT
        <rfc822;linux-wireless@vger.kernel.org>);
        Thu, 16 Aug 2018 05:58:25 -0400
Date: Thu, 16 Aug 2018 02:23:14 +0530
From: Ajay Singh <ajay.kathat@microchip.com>
To: Greg KH <gregkh@linuxfoundation.org>
CC: <devel@driverdev.osuosl.org>, <linux-wireless@vger.kernel.org>,
        <ganesh.krishna@microchip.com>, <aditya.shankar@microchip.com>,
        <nicolas.ferre@microchip.com>, <claudiu.beznea@microchip.com>,
        <adham.abozaeid@microchip.com>
Subject: Re: feedback on mainlining wilc1000 staging driver
Message-ID: <20180816022314.32204302@ajaysk-VirtualBox> (sfid-20180816_090209_814775_A3E2FEE4)
In-Reply-To: <20180816064354.GA2564@kroah.com>
References: <20180816015243.545cd009@ajaysk-VirtualBox>
        <20180816064354.GA2564@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

Hi Greg,

On Thu, 16 Aug 2018 08:43:54 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:

> On Thu, Aug 16, 2018 at 01:52:43AM +0530, Ajay Singh wrote:
> > Hi Greg,
> > 
> > We all are working on submitting and reviewing patches for wilc1000
> > in staging driver for quite some time. 
> > 
> > We would like to have feedback on the next steps to bring wilc1000
> > driver closer to move into the wireless subsystem tree.   
> 
> <snip>
> 
> It is the middle of the merge window, combined with all of the 1ltf
> crap, and other stable stuff.  Can you wait until after the merge
> window for this please?  There's nothing we can do now anyway.
> Submit the rest of your pending patches, get those merged and then we
> can review the code to see what you have left to do.
> 

Thanks for your time.
I can wait till the end of merge window to discuss this. 
My intention is not to send changes during the current merge window
but to understand what is pending for our driver.
Let's revisit this later as you have suggested.

Regards,
Ajay