From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: serialmidi change breaks build on 2.6.10-rc2-mm2
Date: Wed, 24 Nov 2004 11:45:16 +0100 [thread overview]
Message-ID: <s5hoehnpltv.wl@alsa2.suse.de> (raw)
In-Reply-To: <1101252663.5207.7.camel@krustophenia.net>
At Tue, 23 Nov 2004 18:31:02 -0500,
Lee Revell wrote:
>
> Rather than fixing anything this change actually broke compilation on my
> kernel. Is this change only in the latest rc or Linus' BK tree?
The patch is needed for Linus 2.6.10-rc2.
I checked 2.6.10-rc2-mm3 now, but it doesn't contain any change to
tty_driver.*. Could you recheck the build with mm?
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-11-24 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 23:31 serialmidi change breaks build on 2.6.10-rc2-mm2 Lee Revell
2004-11-24 10:45 ` Takashi Iwai [this message]
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=s5hoehnpltv.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
/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