From: Jean Delvare <khali@linux-fr.org>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Andy Walls <awalls@radix.net>, linux-media@vger.kernel.org
Subject: Re: General protection fault on rmmod cx8800
Date: Tue, 3 Mar 2009 22:33:25 +0100 [thread overview]
Message-ID: <20090303223325.7a6f0f94@hyperion.delvare> (raw)
In-Reply-To: <Pine.LNX.4.58.0903031212550.24268@shell2.speakeasy.net>
On Tue, 3 Mar 2009 12:14:06 -0800 (PST), Trent Piepho wrote:
> On Tue, 3 Mar 2009, Jean Delvare wrote:
> > On Tue, 3 Mar 2009 01:40:00 -0800 (PST), Trent Piepho wrote:
> > > On Mon, 2 Mar 2009, Jean Delvare wrote:
> > > In 2.6.20 delayed_work was split from work_struct. The concept of delayed
> > > work was already there and schedule_delayed_work() hasn't changed. I think
> > > this can also be handled with a compat.h change that defines delayed_work
> > > to work_struct. That will only be a problem on pre 2.6.20 kernels if some
> > > code decides to define identifiers named work_struct and delayed_work in
> > > the same scope. There are currently no identifier named delayed_work in
> > > any driver and one driver (sq905) has a structure member named
> > > work_struct. So I think it'll be ok.
> >
> > Wow, I didn't expect that many different compatibility issues. This
> > goes beyond the time I am ready to spend on it, I'm afraid.
>
> I already have a patch for compat.h that handles the last remaining issue.
> You don't have to do anything.
Ah, very nice then. Please push it to the v4l-dvb repository so that I
can send my own patch. I will also fix the 3 other drivers that have
the same bug (ir-kbd-i2c, saa6588 and em28xx-input).
--
Jean Delvare
next prev parent reply other threads:[~2009-03-03 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 20:41 General protection fault on rmmod cx8800 Jean Delvare
2009-03-02 12:39 ` Jean Delvare
2009-03-02 14:16 ` Andy Walls
2009-03-02 16:03 ` Jean Delvare
2009-03-02 19:05 ` Jean Delvare
2009-03-02 21:12 ` Trent Piepho
2009-03-02 21:52 ` Jean Delvare
2009-03-03 9:40 ` Trent Piepho
2009-03-03 9:49 ` Trent Piepho
2009-03-03 12:16 ` Jean Delvare
2009-03-03 20:14 ` Trent Piepho
2009-03-03 21:33 ` Jean Delvare [this message]
2009-03-02 22:33 ` Andy Walls
2009-03-02 20:09 ` Andy Walls
2009-03-05 5:09 ` Trent Piepho
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=20090303223325.7a6f0f94@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=awalls@radix.net \
--cc=linux-media@vger.kernel.org \
--cc=xyzzy@speakeasy.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