From: Kalle Valo <kvalo@codeaurora.org>
To: <Ajay.Kathat@microchip.com>
Cc: <linux-wireless@vger.kernel.org>, <devel@driverdev.osuosl.org>,
<gregkh@linuxfoundation.org>, <johannes@sipsolutions.net>,
<Nicolas.Ferre@microchip.com>, <Claudiu.Beznea@microchip.com>,
<Sripad.Balwadgi@microchip.com>,
<Venkateswara.Kaja@microchip.com>
Subject: Re: [PATCH] wilc1000: move wilc driver out of staging
Date: Thu, 02 Jul 2020 11:43:07 +0300 [thread overview]
Message-ID: <875zb6b944.fsf@codeaurora.org> (raw)
In-Reply-To: <a09157e8-6464-9d48-5d5d-fc168e1b85dc@microchip.com> (Ajay Kathat's message of "Thu, 2 Jul 2020 07:30:31 +0000")
<Ajay.Kathat@microchip.com> 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@microchip.com> writes:
>>
>>> From: Ajay Singh <ajay.kathat@microchip.com>
>>>
>>> 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@microchip.com/
>>> [2].
>>> https://lore.kernel.org/linux-wireless/1562896697-8002-1-git-send-email-ajay.kathat@microchip.com/
>>>
>>> Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
>>> ---
>>>
>>> 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@microchip.com/
>>
>> 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
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: <Ajay.Kathat@microchip.com>
Cc: devel@driverdev.osuosl.org, Venkateswara.Kaja@microchip.com,
Sripad.Balwadgi@microchip.com, gregkh@linuxfoundation.org,
linux-wireless@vger.kernel.org, Nicolas.Ferre@microchip.com,
johannes@sipsolutions.net
Subject: Re: [PATCH] wilc1000: move wilc driver out of staging
Date: Thu, 02 Jul 2020 11:43:07 +0300 [thread overview]
Message-ID: <875zb6b944.fsf@codeaurora.org> (raw)
In-Reply-To: <a09157e8-6464-9d48-5d5d-fc168e1b85dc@microchip.com> (Ajay Kathat's message of "Thu, 2 Jul 2020 07:30:31 +0000")
<Ajay.Kathat@microchip.com> 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@microchip.com> writes:
>>
>>> From: Ajay Singh <ajay.kathat@microchip.com>
>>>
>>> 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@microchip.com/
>>> [2].
>>> https://lore.kernel.org/linux-wireless/1562896697-8002-1-git-send-email-ajay.kathat@microchip.com/
>>>
>>> Signed-off-by: Ajay Singh <ajay.kathat@microchip.com>
>>> ---
>>>
>>> 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@microchip.com/
>>
>> 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
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2020-07-02 8:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 12:37 [PATCH] wilc1000: move wilc driver out of staging Ajay.Kathat
2020-06-25 12:37 ` Ajay.Kathat
2020-06-26 5:36 ` kernel test robot
2020-06-26 5:36 ` kernel test robot
2020-06-26 5:36 ` kernel test robot
2020-06-26 5:51 ` Kalle Valo
2020-06-26 5:51 ` Kalle Valo
2020-06-26 6:46 ` Ajay.Kathat
2020-06-26 6:46 ` Ajay.Kathat
2020-06-30 6:03 ` kernel test robot
2020-07-02 7:00 ` Kalle Valo
2020-07-02 7:00 ` Kalle Valo
2020-07-02 7:15 ` Greg KH
2020-07-02 7:15 ` Greg KH
2020-07-02 7:24 ` Ajay.Kathat
2020-07-02 7:24 ` Ajay.Kathat
2020-07-02 7:30 ` Greg KH
2020-07-02 7:30 ` Greg KH
2020-07-02 7:30 ` Ajay.Kathat
2020-07-02 7:30 ` Ajay.Kathat
2020-07-02 8:43 ` Kalle Valo [this message]
2020-07-02 8:43 ` 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=875zb6b944.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Ajay.Kathat@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=Sripad.Balwadgi@microchip.com \
--cc=Venkateswara.Kaja@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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.