On 07/21/2017 10:51 PM, Greg KH wrote:
On Fri, Jul 21, 2017 at 07:36:41PM -0500, Larry Finger wrote:
On 07/21/2017 10:08 AM, Greg KH wrote:
On Thu, Jul 20, 2017 at 08:18:13PM -0500, Larry Finger wrote:
Kalle and Greg,
Once again I find myself in the awkward position of needing to submit code
On 22-07-17 20:43, Hans de Goede wrote:
> The real culprit here seems to be:
>
> jul 22 14:13:23 localhost.localdomain kernel: brcmfmac:
> brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
So I dug a little deeper in our firmware and as it turns out it is
indeed a firmware halt which is
On 22-07-17 21:19, Ian Molton wrote:
> On 22/07/17 20:18, Ian Molton wrote:
>> On 22/07/17 19:43, Hans de Goede wrote:
>>> Hi,
>>>
>>> When upgrading my devel environment to 4.13-rc1+ I noticed that
>>> the brcm43430 sdio wifi on a Chuwi Hi8 plus stopped working:
>>
>> There is a fix for this:
>>
Hi Andy,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.13-rc1]
[cannot apply to next-20170721]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
> Arend van Spriel hat am 22. Juli 2017 um 21:40
> geschrieben:
>
>
> On 22-07-17 15:18, Stefan Wahren wrote:
> > Hi,
> >
> > with enabled memleak detector on 4.13-rc1 (Raspberry Pi Zero W) i get the
> > following:
> >
> > root@raspberrypi:/sys/kernel/debug#
Hi Ard,
[auto build test ERROR on cryptodev/master]
[also build test ERROR on v4.13-rc1 next-20170721]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 22 July 2017 at 20:53, Arend van Spriel wrote:
> On 22-07-17 21:19, Ian Molton wrote:
>> On 22/07/17 20:18, Ian Molton wrote:
>>> On 22/07/17 19:43, Hans de Goede wrote:
Hi,
When upgrading my devel environment to 4.13-rc1+ I noticed that
the
Hi Andy,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc1]
[cannot apply to next-20170721]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Andy,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc1 next-20170721]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 22-07-17 15:18, Stefan Wahren wrote:
> Hi,
>
> with enabled memleak detector on 4.13-rc1 (Raspberry Pi Zero W) i get the
> following:
>
> root@raspberrypi:/sys/kernel/debug# cat kmemleak
> unreferenced object 0xd824e400 (size 1024):
> comm "kworker/0:0", pid 3, jiffies 4294939822 (age
Hi,
When upgrading my devel environment to 4.13-rc1+ I noticed that
the brcm43430 sdio wifi on a Chuwi Hi8 plus stopped working:
jul 22 14:13:23 localhost.localdomain kernel: brcmfmac: brcmf_sdio_probe:
Loading firmware brcm/brcmfmac43430-sdio.bin for chip a9a6 rev 0001
jul 22 14:13:23
On 22/07/17 20:18, Ian Molton wrote:
> On 22/07/17 19:43, Hans de Goede wrote:
>> Hi,
>>
>> When upgrading my devel environment to 4.13-rc1+ I noticed that
>> the brcm43430 sdio wifi on a Chuwi Hi8 plus stopped working:
>
> There is a fix for this:
>
> https://patchwork.kernel.org/patch/9836383/
On 22/07/17 19:43, Hans de Goede wrote:
> Hi,
>
> When upgrading my devel environment to 4.13-rc1+ I noticed that
> the brcm43430 sdio wifi on a Chuwi Hi8 plus stopped working:
There is a fix for this:
https://patchwork.kernel.org/patch/9836383/
IIRC
-Ian
Hi,
with enabled memleak detector on 4.13-rc1 (Raspberry Pi Zero W) i get the
following:
root@raspberrypi:/sys/kernel/debug# cat kmemleak
unreferenced object 0xd824e400 (size 1024):
comm "kworker/0:0", pid 3, jiffies 4294939822 (age 873.420s)
hex dump (first 32 bytes):
00 00 00 00 00 00
On Sat, Jul 22, 2017 at 07:51:20AM -0500, Larry Finger wrote:
> On 07/21/2017 10:51 PM, Greg KH wrote:
> > On Fri, Jul 21, 2017 at 07:36:41PM -0500, Larry Finger wrote:
> > > On 07/21/2017 10:08 AM, Greg KH wrote:
> > > > On Thu, Jul 20, 2017 at 08:18:13PM -0500, Larry Finger wrote:
> > > > >
On Sun, Jul 09, 2017 at 01:08:58PM +0200, Johan Hovold wrote:
> A recent change fixing NFC device allocation itself introduced an
> error-handling bug by returning an error pointer in case device-id
> allocation failed. This is clearly broken as the callers still expected
> NULL to be returned on
16 matches
Mail list logo