From: Ajay Singh <ajay.kathat@microchip.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Nicolas Ferre - M43238" <Nicolas.Ferre@microchip.com>,
Ganesh Krishna - C00112 <Ganesh.Krishna@microchip.com>,
Adham Abozaeid - C43058 <Adham.Abozaeid@microchip.com>,
Aditya Shankar - I16078 <Aditya.Shankar@microchip.com>
Subject: Re: feedback on mainlining wilc1000 staging driver
Date: Fri, 5 Oct 2018 08:03:00 +0530 [thread overview]
Message-ID: <20181005080300.5030f616@ajaysk-VirtualBox> (raw)
In-Reply-To: <871s953nhu.fsf@codeaurora.org>
Hi Kalle,
On Thu, 4 Oct 2018 15:27:57 +0300
Kalle Valo <kvalo@codeaurora.org> wrote:
> Ajay Singh <ajay.kathat@microchip.com> writes:
>
> > Hi Kalle,
> >
> > On Thu, 23 Aug 2018 16:37:45 +0530
> > Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> >> Ajay Singh <ajay.kathat@microchip.com> writes:
> >>
> >> >> >>> We need help to review and identify if there are any pending
> >> >> >>> items for wilc1000 driver, so we can address those issues
> >> >> >>> and make it ready to move to the wireless subsystem.
> >> >> >>
> >> >> >> I think the best way to get that forward is to submit a patch
> >> >> >> (or patchset) to linux-wireless, that's the easiest for
> >> >> >> reviewers.
> >> >> >
> >> >> > For brcm80211 drivers we used a single patch introducing it
> >> >> > under the wireless drivers folder. Because it was quite a
> >> >> > sizable patch we parked it on the wireless wiki page. Had a
> >> >> > few iterations doing it like that.
> >> >>
> >> >> Another option is to split it so that there's one patch per
> >> >> file, should be even pretty easy to automate that. It's just so
> >> >> much easier to comment on a patch submitted by email compared
> >> >> to the reviewer manually copying code and then commenting it,
> >> >> yuck.
> >> >
> >> > Sure. I will prepare a patch per file send for review as its
> >> > easy to review.
> >> >
> >> > As Greg suggested, I will wait for the merge window to close and
> >> > after completing pending patches to staging, I will start the
> >> > review.
> >> >
> >> > For my understanding, the patches for review will be based on
> >> > wireless-testing branch.
> >>
> >> In this case I think wireless-drivers-next is the safest choise,
> >> wireless-testing also has other trees which might cause conflicts
> >> etc.
> >
> > I have submitted a patch series for wilc1000 driver, single file
> > per patch and its based on wireless-drivers-next.
> > I hope its done correctly, please provide inputs so we can
> > address and make this driver ready for mainline.
>
> Thanks, I see it in patchwork:
>
> https://patchwork.kernel.org/project/linux-wireless/list/?series=23251&state=*&order=date
>
> Do note that we have also another new driver (rtwlan/rtw88) under
> review so review from the wireless folks might take some time.
>
Thanks for the update.
Btw I could see our driver was added to the pending branch. Just
curious, could you please share details about how the pending branch is
used ?
Regards,
Ajay
next prev parent reply other threads:[~2018-10-05 2:33 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
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 [this message]
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=20181005080300.5030f616@ajaysk-VirtualBox \
--to=ajay.kathat@microchip.com \
--cc=Adham.Abozaeid@microchip.com \
--cc=Aditya.Shankar@microchip.com \
--cc=Ganesh.Krishna@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=arend.vanspriel@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--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 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).