linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	linuxppc-dev@ozlabs.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Benjamin@ozlabs.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] AOA: Convert onyx and tas codecs to new-style i2c    drivers
Date: Wed, 15 Apr 2009 10:19:36 +0200	[thread overview]
Message-ID: <20090415101936.7f6d720e@hyperion.delvare> (raw)
In-Reply-To: <m2prfe26on.fsf@igel.home>

On Wed, 15 Apr 2009 00:48:08 +0200, Andreas Schwab wrote:
> Jean Delvare <khali@linux-fr.org> writes:
> 
> > Hi Johannes,
> >
> > On Tue, 14 Apr 2009 19:41:55 +0200, Johannes Berg wrote:
> >> Alright, with the patch Andreas pointed out it loads, but segfaults, as
> >> below. Works fine without your patch.
> >
> > Thanks for the quick test and sorry that it didn't work. I'll take a
> > look at the trace below and try to figure out what went wrong.
> >
> > Did you remove the 2 MODULE_DEVICE_TABLE from my patch? If you didn't,
> > please pick the latest version of my patch which doesn't have them:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/jdelvare/linux-2.6/jdelvare-i2c/sound-aoa-codecs-convert-to-new-style.patch
> > I don't think they are the reason of the crash, but who knows...
> 
> I tried with a tas-based iBook, and it works fine here.

Good news, thanks Andreas!

-- 
Jean Delvare

  reply	other threads:[~2009-04-15  8:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 13:02 [PATCH] AOA: Convert onyx and tas codecs to new-style i2c drivers Jean Delvare
2009-04-08 15:51 ` Johannes Berg
2009-04-08 20:48   ` Jean Delvare
2009-04-09  7:44     ` Johannes Berg
2009-04-09 12:19       ` Jean Delvare
2009-04-09 12:34         ` Johannes Berg
2009-04-09 14:21           ` Jean Delvare
2009-04-10 15:02         ` Jean Delvare
2009-04-14 14:37           ` Jean Delvare
2009-04-14 14:45             ` Takashi Iwai
2009-04-16  7:53               ` Jean Delvare
2009-04-16  7:56                 ` Takashi Iwai
2009-04-14 15:40         ` Johannes Berg
2009-04-14 15:50           ` Johannes Berg
2009-04-14 16:57             ` Jean Delvare
2009-04-14 17:41             ` Johannes Berg
2009-04-14 19:49               ` Jean Delvare
2009-04-14 21:59                 ` Johannes Berg
2009-04-15 12:15                   ` Jean Delvare
2009-04-15 12:52                     ` Johannes Berg
2009-04-15 13:06                       ` Jean Delvare
2009-04-15 13:18                         ` Johannes Berg
2009-04-15 13:52                           ` Jean Delvare
2009-04-14 22:48                 ` Andreas Schwab
2009-04-15  8:19                   ` Jean Delvare [this message]
2009-04-14 16:48           ` Andreas Schwab
2009-04-14 17:20             ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2009-04-20 20:54 Jean Delvare
2009-04-20 21:04 ` Johannes Berg
2009-04-21  9:29   ` Jean Delvare
2009-04-21  9:41     ` Johannes Berg
2009-04-21  6:30 ` Takashi Iwai

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=20090415101936.7f6d720e@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=Benjamin@ozlabs.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=schwab@linux-m68k.org \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).