From: Takashi Iwai <tiwai@suse.de>
To: Hubert Tonneau <hubert.tonneau@fullpliant.org>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.18-rc3
Date: Wed, 02 Aug 2006 16:58:26 +0200 [thread overview]
Message-ID: <s5h7j1rjib1.wl%tiwai@suse.de> (raw)
In-Reply-To: <06AZVN211@briare1.heliogroup.fr>
At Wed, 02 Aug 2006 18:35:26 GMT,
Hubert Tonneau wrote:
>
> Takashi Iwai wrote:
> >
> > Do you really get Oops with 2.6.17-final, too?
> > AFAIK, there was a bug in the early 2.6.17-rc regarding OSS emulation,
> > but it got fixed in the later rc.
>
> I confirm that the only oops I got was with 2.6.17-rc1
>
> > The behavior of invalid O_* flag seems incompatible with the older
> > version. Although I don't think it's totally wrong behavior, surely
> > better to keep the compatibility. The patch below should fix it.
>
> I don't care: I have changed my player.
> I also tend to agree that opening /dev/dsp read write was not a good
> idea, so I would not criticise the new behaviour.
Well, incompatibility is worse in most cases than rationality.
Could you test the patch really fixes your case, so that I can push it
to 2.6.17-stable tree?
> Each version of Linux 2.6 tend to break some softwares due to subtil
> changes. What is bad is that these changes tend to be not announced,
> but on the other hand the kernel mailing list is very responsive,
> so all in all it might be a reasonable way to go.
It was an unintentioal change, so it's not somthing to be announced ;)
It's a thing just to be fixed.
Takashi
next prev parent reply other threads:[~2006-08-02 14:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 18:35 Hubert Tonneau
2006-08-02 14:58 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 16:37 Hubert Tonneau
2006-08-04 17:52 ` Greg KH
2006-08-04 17:55 ` Takashi Iwai
2006-07-30 17:42 Hubert Tonneau
2006-08-02 10:41 ` Takashi Iwai
2006-07-30 16:49 Hubert Tonneau
2006-07-30 16:05 Hubert Tonneau
2006-07-30 13:03 Hubert Tonneau
2006-07-30 9:32 ` Jiri Slaby
2006-07-30 9:42 ` Greg KH
2006-07-30 12:56 Hubert Tonneau
2006-07-30 12:21 Hubert Tonneau
2006-07-30 8:43 ` Arjan van de Ven
2006-07-30 8:51 ` Greg KH
2006-07-30 11:10 ` Alistair John Strachan
2006-07-30 6:27 Linus Torvalds
2006-07-30 8:30 ` Russell King
2006-07-31 8:02 ` Junio C Hamano
2006-07-31 4:13 ` Jesse Brandeburg
2006-07-31 4:27 ` Andrew Morton
2006-07-31 14:54 ` Alan Stern
2006-07-31 15:11 ` Andrew Morton
2006-07-31 15:59 ` Alan Stern
2006-07-31 20:34 ` Alan Stern
2006-08-02 4:31 ` Jesse Brandeburg
2006-08-02 4:59 ` Andrew Morton
2006-08-02 19:57 ` Jesse Brandeburg
2006-08-02 20:16 ` Rafael J. Wysocki
2006-08-02 20:23 ` Russell King
2006-08-02 20:26 ` Rafael J. Wysocki
2006-08-02 20:32 ` Dave Jones
2006-08-02 20:58 ` Russell King
2006-08-02 21:01 ` Dave Jones
2006-08-02 21:18 ` Linus Torvalds
2006-08-02 21:38 ` Russell King
2006-08-02 22:04 ` Linus Torvalds
2006-08-02 22:05 ` Russell King
2006-08-03 15:58 ` Avuton Olrich
2006-08-03 16:40 ` Adrian Bunk
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=s5h7j1rjib1.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=greg@kroah.com \
--cc=hubert.tonneau@fullpliant.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®