public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Marek <mmarek@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] headers_check: special case seqbuf_dump()
Date: Thu, 16 Jan 2014 13:39:24 +0100	[thread overview]
Message-ID: <1389875964.4985.14.camel@x220> (raw)
In-Reply-To: <s5h4n54ta77.wl%tiwai@suse.de>

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.

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?".


Paul Bolle


  reply	other threads:[~2014-01-16 12:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 10:48 [PATCH] headers_check: special case seqbuf_dump() Paul Bolle
2014-01-15 13:28 ` Arnd Bergmann
2014-01-16 11:53 ` Takashi Iwai
2014-01-16 12:39   ` Paul Bolle [this message]
2014-01-16 13:51     ` 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=1389875964.4985.14.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --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