From: Jeremiah Mahler <jmmahler@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the driver-core tree with the net-next tree
Date: Wed, 3 Dec 2014 13:41:28 -0800 [thread overview]
Message-ID: <20141203214128.GB8974@hudson.localdomain> (raw)
In-Reply-To: <20141203210659.GA8974@hudson.localdomain>
On Wed, Dec 03, 2014 at 01:06:59PM -0800, Jeremiah Mahler wrote:
> Arend,
>
> On Wed, Dec 03, 2014 at 01:49:00PM +0100, Arend van Spriel wrote:
> > On 12/03/14 11:51, Jeremiah Mahler wrote:
> > >On Wed, Dec 03, 2014 at 12:36:55AM -0800, Jeremiah Mahler wrote:
> > >>all,
> > >>
> > >>On Mon, Dec 01, 2014 at 08:34:05AM +0100, Arend van Spriel wrote:
> > >>>On 01-12-14 08:19, Stephen Rothwell wrote:
> > >>>>Hi Greg,
> > >>>>
[...]
> > >
> > >I took a look at the patch that is causing this problem (d32394fae95).
> > >My config negates everything in the patch except for a one line change
> > >to ath9k/pci.c. If I remove this change (shown below) the problem goes
> > >away.
> >
> > Ok. But then it will likely crash when you cat one of the changed debugfs
> > files. Guess this commit needs to be reverted entirely.
> >
>
> On my machine ATH9K_DEBUFS is disabled so none of that code is used.
>
> I can try enabling it and see if a cat will crash it.
>
With ATH9K_DEBUGFS enabled, cat works fine on the files that were
changed.
/sys/kernel/debug/ieee80211/phy0/ath9k/
dma
interrupt
xmit
queues
> > Regards,
> > Arend
> >
[...]
>
> --
> - Jeremiah Mahler
--
- Jeremiah Mahler
next prev parent reply other threads:[~2014-12-03 21:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 7:19 linux-next: manual merge of the driver-core tree with the net-next tree Stephen Rothwell
2014-12-01 7:19 ` Stephen Rothwell
2014-12-01 7:34 ` Arend van Spriel
2014-12-01 7:34 ` Arend van Spriel
2014-12-03 8:36 ` Jeremiah Mahler
2014-12-03 10:51 ` Jeremiah Mahler
2014-12-03 12:49 ` Arend van Spriel
2014-12-03 12:49 ` Arend van Spriel
2014-12-03 16:21 ` Greg KH
2014-12-03 20:07 ` Arend van Spriel
2014-12-03 20:07 ` Arend van Spriel
2014-12-03 21:06 ` Jeremiah Mahler
2014-12-03 21:41 ` Jeremiah Mahler [this message]
2014-12-04 10:19 ` Jeremiah Mahler
2014-12-04 11:41 ` Arend van Spriel
-- strict thread matches above, loose matches on Subject: below --
2023-01-30 4:32 Stephen Rothwell
2023-01-30 12:31 ` Andy Shevchenko
2023-01-30 16:00 ` Greg KH
2018-07-23 5:12 Stephen Rothwell
2018-07-23 6:20 ` Greg KH
2018-08-15 23:42 ` Stephen Rothwell
2018-08-16 0:05 ` Rajat Jain
2013-08-01 5:21 Stephen Rothwell
2013-08-01 5:21 ` Stephen Rothwell
2013-08-02 0:28 ` Greg KH
2013-02-04 4:38 Stephen Rothwell
2013-02-04 4:38 ` Stephen Rothwell
2013-02-04 4:59 ` Greg KH
2013-02-04 4:34 Stephen Rothwell
2013-02-04 4:34 ` Stephen Rothwell
2011-10-25 8:07 Stephen Rothwell
2011-10-25 8:07 ` Stephen Rothwell
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=20141203214128.GB8974@hudson.localdomain \
--to=jmmahler@gmail.com \
--cc=arend@broadcom.com \
--cc=linux-kernel@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.