linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ajay Singh <ajay.kathat@microchip.com>
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
Date: Thu, 16 Aug 2018 08:43:54 +0200	[thread overview]
Message-ID: <20180816064354.GA2564@kroah.com> (raw)
In-Reply-To: <20180816015243.545cd009@ajaysk-VirtualBox>

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,

greg k-h

  reply	other threads:[~2018-08-16  9:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 20:22 feedback on mainlining wilc1000 staging driver Ajay Singh
2018-08-16  6:43 ` Greg KH [this message]
2018-08-15 20:53   ` Ajay Singh
2018-08-16 10:47 ` Kalle Valo
2018-08-16 10:53   ` Kalle Valo
2018-08-17  4:32     ` Ajay Singh
2018-08-17  7:49       ` Kalle Valo
2018-08-17  8:21         ` Arend van Spriel
2018-08-17  8:36           ` Kalle Valo
2018-08-17  9:09             ` Ajay Singh
2018-08-23 11:07               ` Kalle Valo
2018-09-26 10:27                 ` Ajay Singh
2018-10-04 12:27                   ` Kalle Valo
2018-10-05  2:33                     ` Ajay Singh
2018-10-05  5:16                       ` Kalle Valo

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=20180816064354.GA2564@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adham.abozaeid@microchip.com \
    --cc=aditya.shankar@microchip.com \
    --cc=ajay.kathat@microchip.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ganesh.krishna@microchip.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nicolas.ferre@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).