All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, linux-media@vger.kernel.org
Subject: Re: NULL pointer dereference in ALSA triggered	through saa7134-alsa
Date: Mon, 10 Aug 2009 19:06:29 +0300	[thread overview]
Message-ID: <4A804585.9060908@pardus.org.tr> (raw)
In-Reply-To: <s5hocqnllcg.wl%tiwai@suse.de>

Takashi Iwai wrote:
> But /usr/include/sound isn't used for building kernel modules normally.
> Unless any hack is added, these files have to be installed to the
> kernel header directory.
>   

Ah you're right, I totally missed that one. Thanks, will try to
workaround that.

WARNING: multiple messages have this Message-ID (diff)
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, linux-media@vger.kernel.org
Subject: Re: [alsa-devel] NULL pointer dereference in ALSA triggered	through saa7134-alsa
Date: Mon, 10 Aug 2009 19:06:29 +0300	[thread overview]
Message-ID: <4A804585.9060908@pardus.org.tr> (raw)
In-Reply-To: <s5hocqnllcg.wl%tiwai@suse.de>

Takashi Iwai wrote:
> But /usr/include/sound isn't used for building kernel modules normally.
> Unless any hack is added, these files have to be installed to the
> kernel header directory.
>   

Ah you're right, I totally missed that one. Thanks, will try to
workaround that.

  reply	other threads:[~2009-08-10 16:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 13:50 NULL pointer dereference in ALSA triggered through saa7134-alsa Ozan Çağlayan
2009-08-10 13:50 ` Ozan Çağlayan
2009-08-10 14:00 ` Takashi Iwai
2009-08-10 14:00   ` [alsa-devel] " Takashi Iwai
2009-08-10 15:42   ` Ozan Çağlayan
2009-08-10 15:42     ` [alsa-devel] " Ozan Çağlayan
2009-08-10 15:50     ` Takashi Iwai
2009-08-10 15:50       ` Takashi Iwai
2009-08-10 16:06       ` Ozan Çağlayan [this message]
2009-08-10 16:06         ` Ozan Çağlayan
2009-08-10 16:11         ` Takashi Iwai
2009-08-10 16:11           ` Takashi Iwai
2009-08-10 18:28           ` Ozan Çağlayan
2009-08-10 19:08             ` Ozan Çağlayan

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=4A804585.9060908@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-media@vger.kernel.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 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.