From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752595AbaAPNv5 (ORCPT ); Thu, 16 Jan 2014 08:51:57 -0500 Received: from cantor2.suse.de ([195.135.220.15]:43326 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751389AbaAPNv4 (ORCPT ); Thu, 16 Jan 2014 08:51:56 -0500 Date: Thu, 16 Jan 2014 14:51:53 +0100 Message-ID: From: Takashi Iwai To: Paul Bolle Cc: Arnd Bergmann , Andrew Morton , Michal Marek , linux-kernel@vger.kernel.org Subject: Re: [PATCH] headers_check: special case seqbuf_dump() In-Reply-To: <1389875964.4985.14.camel@x220> References: <1389782899.2128.15.camel@x220> <1389875964.4985.14.camel@x220> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Thu, 16 Jan 2014 13:39:24 +0100, Paul Bolle wrote: > > On Thu, 2014-01-16 at 12:53 +0100, Takashi Iwai wrote: > > At Wed, 15 Jan 2014 11:48:19 +0100, > > Paul Bolle wrote: > > > 2) By the way, what is actually meant by: > > > It is no longer possible to actually link against OSSlib with this > > > header, but we still provide these macros for programs using them. > > > > > > Doesn't that mean compatibility to OSSlib isn't even useful? > > > > Well, it's not about the compatibility to osslib. The OSS seq > > user-space codes are written with these macros no matter whether to > > use osslib or not. osslib was newer than these macros and it was > > designed to be compatible with them. > > So perhaps that line should read something like: > [...] > header, but we still provide these macros for programs that want to > interface with /dev/dsp and /dev/sequencer directly. The macros are only for /dev/sequencer (and its variants). > I'm making that up: I know nothing about this stuff. I'm just looking > for a way to make that comment clear to a person that wonders in, say, > 2019: "What on earth is seqbuf_dump() good for?". I don't think rephrasing like the above would give a better answer... Takashi