From: Greg KH <gregkh@linuxfoundation.org>
To: Aditya Shankar <aditya.shankar@microchip.com>
Cc: ganesh.krishna@microchip.com, linux-wireless@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Nicolas.Ferre@microchip.com
Subject: Re: [PATCH 2/2] Revert "staging: wilc1000: Replace kthread with workqueue for host interface"
Date: Thu, 6 Oct 2016 12:17:59 +0200 [thread overview]
Message-ID: <20161006101759.GA7799@kroah.com> (raw)
In-Reply-To: <20161006152659.15a4c38b1dc8d4f781c20e0a@microchip.com>
On Thu, Oct 06, 2016 at 03:26:59PM +0530, Aditya Shankar wrote:
> On Fri, 30 Sep 2016 15:22:15 +0200
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > On Fri, Sep 30, 2016 at 03:43:18PM +0530, Aditya Shankar wrote:
> > > This reverts commit 2518ac59eb27 ("staging: wilc1000: Replace kthread
> > > with workqueue for host interface")
> > >
> > > This commit breaks wilc1000 driver init. A crash was seen
> > > everytime the wlan interface was brought up and wilc device
> > > open was attempted. This change is being reverted until we
> > > figure out the problem in this change. The driver is
> > > usable now with this change reverted.
> > >
> > > Signed-off-by: Aditya Shankar <Aditya.Shankar@microchip.com>
> > >
> > > Conflicts:
> > > drivers/staging/wilc1000/host_interface.c
> >
> > What is this line doing here?
> >
> > And shouldn't we add a cc: stable tag as well? Or at the least, put a
> > "fixes:" tag to let people know exactly what commit it is fixing (the
> > id that it is reverting.)
> >
> > thanks,
> >
> > greg k-h
>
> Apologies for this bad commit message.
>
> I have an update on this wilc1000 crash issue. I've figured out
> the cause for the crash and fixed it. Therefore,
> I request you to ignore the patch I sent out to
> revert the change causing the regression. The cause was a misplaced
> call to destroy workqueue soon after creating it.
> With this removed, the issue is not seen.
>
> I will send out a separate patch to fix the issue.
Wonderful, thanks for doing that, I'll drop these and use your fix when
you send it.
greg k-h
prev parent reply other threads:[~2016-10-06 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160930101318.GA24973@aditya-ubuntu.local>
2016-09-30 13:22 ` [PATCH 2/2] Revert "staging: wilc1000: Replace kthread with workqueue for host interface" Greg KH
2016-10-06 9:56 ` Aditya Shankar
2016-10-06 10:17 ` Greg KH [this message]
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=20161006101759.GA7799@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Nicolas.Ferre@microchip.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=linux-kernel@vger.kernel.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).