From: Jindrich Makovicka <makovick@gmail.com>
To: linux-media@vger.kernel.org
Cc: kernel-testers@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kernel-testers@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316
Date: Mon, 14 Jun 2010 14:27:08 +0200 [thread overview]
Message-ID: <20100614142708.668d382e@holly> (raw)
In-Reply-To: <20100614063948.GA3999@x200>
On Mon, 14 Jun 2010 09:39:48 +0300
Alexey Dobriyan <adobriyan@gmail.com>
wrote:
> On Sun, Jun 13, 2010 at 01:57:40PM -0600, Grant Likely wrote:
> > On brief review, they look like completely different issues. I
> > doubt the second patch will fix the flexcop-pci issue.
>
> It will, see how name wht slashes propagated by request_irq()
Yes, the latter patch dodges the issue with flexcop driver by simply
skipping the directory creation, but both patches should be applied IMO.
The former to fix the flexcop driver because we can trivially fix it,
the latter to solve problems with any generic bogus firmware.
--
Jindrich Makovicka
next prev parent reply other threads:[~2010-06-14 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <g77CuMUl7QI.A.5wF.V5OFMB@chimera>
[not found] ` <YPGdyfWGvNK.A.C8B.d9OFMB@chimera>
2010-06-13 15:22 ` [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316 Stefan Lippers-Hollmann
2010-06-13 18:10 ` Christian Kujau
2010-06-13 19:57 ` Grant Likely
2010-06-14 6:39 ` Alexey Dobriyan
2010-06-14 12:27 ` Jindrich Makovicka [this message]
2010-06-14 15:42 ` Grant Likely
[not found] <JzEGxUyyQHG.A.ZtH.YHJ4LB@chimera>
[not found] ` <8VO9AsMlpMD.A.IFC.aKJ4LB@chimera>
2010-05-05 0:18 ` Stefan Lippers-Hollmann
2010-05-05 0:23 ` Rafael J. Wysocki
[not found] <deuQKFRcc0B.A.3EG.BRSzLB@tosh>
[not found] ` <YeFfFNFyTSF.A.vUB.fSSzLB@tosh>
2010-04-30 2:44 ` Stefan Lippers-Hollmann
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=20100614142708.668d382e@holly \
--to=makovick@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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