From: Jean Delvare <khali@linux-fr.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Christian Kujau <lists@nerdbynature.de>,
linuxppc-dev@ozlabs.org,
Michael Hanselmann <linux-kernel@hansmi.ch>,
LKML <linux-kernel@vger.kernel.org>,
Stelian Pop <stelian@popies.net>
Subject: Re: i2c_powermac: Kernel access of bad area
Date: Sat, 30 Jan 2010 10:35:52 +0100 [thread overview]
Message-ID: <20100130103552.284209fb@hyperion.delvare> (raw)
In-Reply-To: <1264800895.20211.120.camel@pasglop>
On Sat, 30 Jan 2010 08:34:55 +1100, Benjamin Herrenschmidt wrote:
>
> > Ben, what about applying this patch of mine, as Christian reported it
> > fixed his oops?
>
> Sure. I never quite know with i2c which ones you will apply directly and
> which ones you want to go through my tree :-)
>
> Hopefully they should still be referened on patchwork, I'll dig there
> and pick them up.
Well, basically I pick patches that touch drivers/i2c/*, and I don't
pick patches that touch drivers/macintosh/*. When I can't build the
drivers, I don't really feel like pushing the patches myself.
--
Jean Delvare
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Christian Kujau <lists@nerdbynature.de>,
linuxppc-dev@ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
Stelian Pop <stelian@popies.net>,
Michael Hanselmann <linux-kernel@hansmi.ch>
Subject: Re: i2c_powermac: Kernel access of bad area
Date: Sat, 30 Jan 2010 10:35:52 +0100 [thread overview]
Message-ID: <20100130103552.284209fb@hyperion.delvare> (raw)
In-Reply-To: <1264800895.20211.120.camel@pasglop>
On Sat, 30 Jan 2010 08:34:55 +1100, Benjamin Herrenschmidt wrote:
>
> > Ben, what about applying this patch of mine, as Christian reported it
> > fixed his oops?
>
> Sure. I never quite know with i2c which ones you will apply directly and
> which ones you want to go through my tree :-)
>
> Hopefully they should still be referened on patchwork, I'll dig there
> and pick them up.
Well, basically I pick patches that touch drivers/i2c/*, and I don't
pick patches that touch drivers/macintosh/*. When I can't build the
drivers, I don't really feel like pushing the patches myself.
--
Jean Delvare
next prev parent reply other threads:[~2010-01-30 9:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 4:40 i2c_powermac: Kernel access of bad area Christian Kujau
2009-12-29 4:40 ` Christian Kujau
2009-12-29 9:34 ` Benjamin Herrenschmidt
2009-12-29 9:34 ` Benjamin Herrenschmidt
2010-01-06 16:37 ` Jean Delvare
2010-01-06 19:14 ` Christian Kujau
2010-01-06 19:14 ` Christian Kujau
2010-01-07 3:41 ` Christian Kujau
2010-01-07 3:41 ` Christian Kujau
[not found] ` <20100107171738.2c83b13e@hyperion.delvare>
2010-01-29 8:18 ` Jean Delvare
2010-01-29 8:18 ` Jean Delvare
2010-01-29 21:34 ` Benjamin Herrenschmidt
2010-01-29 21:34 ` Benjamin Herrenschmidt
2010-01-30 9:35 ` Jean Delvare [this message]
2010-01-30 9:35 ` Jean Delvare
2010-01-30 6:03 ` Christian Kujau
2010-01-30 6:03 ` Christian Kujau
2010-01-31 6:05 ` Christian Kujau
2010-01-31 6:05 ` Christian Kujau
2010-01-31 9:52 ` Jean Delvare
2010-01-31 9:52 ` Jean Delvare
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=20100130103552.284209fb@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@hansmi.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=stelian@popies.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 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.