linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-wireless@vger.kernel.org,
	Aditya Shankar <Aditya.Shankar@microchip.com>,
	Ganesh Krishna <Ganesh.Krishna@microchip.com>,
	luisbg@osg.samsung.com
Subject: Re: staging: wilc1000: kernel Oops while opening the device
Date: Mon, 19 Sep 2016 15:42:02 +0200	[thread overview]
Message-ID: <20160919134201.GA25769@kroah.com> (raw)
In-Reply-To: <c12338f5-0a50-bb55-0b83-0fa705237cf8@atmel.com>

On Mon, Sep 19, 2016 at 02:06:02PM +0200, Nicolas Ferre wrote:
> Hi all,
> 
> While using the wilc1000 driver with latest 4.8-rc7, I
> have difficulties to open the device and actually use it as I have
> this kernel Oops right after the loading of the firmware (wilc1003_firmware.bin).
> 
> If I revert back the driver to its b9811891a9f60ca9c314dcab3244c65930c4cf37 state,
> it works okay. I did this because I tend to think that it might be related to the latest
> move on this driver to "completion" or "work queues".
> It seems to be a regression from 4.7.

Ick, not good at all.

Any chance you can run 'git bisect' to see if you can find the offending
patch?

I thought the maintainers were testing this driver over time :(

thanks,

greg k-h

  reply	other threads:[~2016-09-19 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 12:06 staging: wilc1000: kernel Oops while opening the device Nicolas Ferre
2016-09-19 13:42 ` Greg Kroah-Hartman [this message]
2016-09-22 12:34   ` Ganesh.Krishna
2016-09-23 13:17     ` Aditya.Shankar
2016-09-23 15:07       ` Greg KH
2016-09-26  5:17         ` Aditya.Shankar
2016-09-27 15:21           ` Greg KH

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=20160919134201.GA25769@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Aditya.Shankar@microchip.com \
    --cc=Ganesh.Krishna@microchip.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    --cc=nicolas.ferre@atmel.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).