From: Jean Delvare <khali@linux-fr.org>
To: "Paweł Sikora" <pluto@agmk.net>
Cc: "Andy Walls" <awalls@radix.net>,
linux-kernel@vger.kernel.org, LMML <linux-media@vger.kernel.org>
Subject: Re: [2.6.31] ir-kbd-i2c oops.
Date: Thu, 1 Oct 2009 12:42:10 +0200 [thread overview]
Message-ID: <20091001124210.4be1dd71@hyperion.delvare> (raw)
In-Reply-To: <op.u039i6wbzu3k57@pawels.alatek.krakow.pl>
On Thu, 01 Oct 2009 12:17:20 +0200, Paweł Sikora wrote:
> Dnia 01-10-2009 o 12:06:09 Jean Delvare <khali@linux-fr.org> napisał(a):
>
> >> I'm not sure if it is the problem here, but it may be prudent to check
> >> that there's no mismatch between the module and the structure
> >> definitions being pulled in via "#include" (maybe by stopping gcc after
> >> the preprocessing with -E ).
> >
> > Thanks for the hint. As far as I can see, this change is new in kernel
> > 2.6.32-rc1. In 2.6.31, which is where Pawel reported the issue, we
> > still have IR_KEYTAB_TYPE.
> >
> > Pawel, are you by any chance mixing kernel drivers of different
> > sources?
>
> everything is under control. i've two separated builds:
> - 2.6.31 from git with debugging patch.
> - vendor kernel from rpms.
> both kernels have separated initrd images for easy booting/testing.
And both have the problem you reported?
--
Jean Delvare
next prev parent reply other threads:[~2009-10-01 10:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 1:00 [2.6.31] ir-kbd-i2c oops Paweł Sikora
2009-09-16 6:57 ` Jean Delvare
2009-09-16 8:03 ` Paweł Sikora
2009-09-29 14:16 ` Jean Delvare
2009-09-29 23:26 ` Hermann Pitton
2009-09-30 8:16 ` Paweł Sikora
2009-09-30 10:57 ` Jean Delvare
2009-09-30 11:52 ` Paweł Sikora
2009-09-30 12:25 ` Jean Delvare
2009-09-30 16:22 ` Paweł Sikora
2009-09-30 23:52 ` Andy Walls
2009-10-01 11:43 ` Jean Delvare
2009-10-03 10:08 ` Paweł Sikora
2009-10-03 12:04 ` Jean Delvare
2009-09-30 23:42 ` Andy Walls
2009-10-01 10:06 ` Jean Delvare
2009-10-01 10:17 ` Paweł Sikora
2009-10-01 10:42 ` Jean Delvare [this message]
2009-10-01 10:47 ` Paweł Sikora
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=20091001124210.4be1dd71@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=awalls@radix.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=pluto@agmk.net \
/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