<Ajay.Kathat@xxxxxxxxxxxxx> writes: > On 02/07/20 12:30 pm, Kalle Valo wrote: >> EXTERNAL EMAIL: Do not click links or open attachments unless you >> know the content is safe >> >> <Ajay.Kathat@xxxxxxxxxxxxx> writes: >> >>> From: Ajay Singh <ajay.kathat@xxxxxxxxxxxxx> >>> >>> WILC1000 is an IEEE 802.11 b/g/n IoT link controller module. The >>> WILC1000 connects to Microchip AVR/SMART MCUs, SMART MPUs, and other >>> processors with minimal resource requirements with a simple >>> SPI/SDIO-to-Wi-Fi interface. >>> >>> WILC1000 driver has been part of staging for few years. With >>> contributions from the community, it has improved significantly. Full >>> driver review has helped in achieving the current state. >>> The details for those reviews are captured in 1 & 2. >>> >>> [1]. >>> https://lore.kernel.org/linux-wireless/1537957525-11467-1-git-send-email-ajay.kathat@xxxxxxxxxxxxx/ >>> [2]. >>> https://lore.kernel.org/linux-wireless/1562896697-8002-1-git-send-email-ajay.kathat@xxxxxxxxxxxxx/ >>> >>> Signed-off-by: Ajay Singh <ajay.kathat@xxxxxxxxxxxxx> >>> --- >>> >>> As suggested, keeping all the changes in single commit with file rename >>> so it's easy to move out of staging [3]. >>> >>> Please choose whichever option you prefer between the git mv or patch series >>> sent last Tuesday. The resulting driver is the same as no patch has been >>> queued in between. >>> >>> [3]. >>> https://lore.kernel.org/linux-wireless/20200623110000.31559-1-ajay.kathat@xxxxxxxxxxxxx/ >> >> As discussed with Greg I created an immutable branch for this and merged >> the branch to wireless-drivers-next: > > Thanks Kalle. > > If my understanding is correct, we have to use 'wireless-driver-next' > master branch to submit new patches for wilc1000. right? Correct. And I also suggest to get familiar with the linux-wireless patchwork to follow patch status, more info in the link below. -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
