From: Jeff Garzik <jgarzik@pobox.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [git patch] fix DocBook build
Date: Wed, 07 Sep 2005 07:27:54 -0400 [thread overview]
Message-ID: <431ECEBA.7040802@pobox.com> (raw)
In-Reply-To: <s5h1x4189ur.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Wed, 07 Sep 2005 12:00:31 +0200,
> I wrote:
>
>>At Wed, 7 Sep 2005 01:17:20 -0400,
>>Jeff Garzik wrote:
>>
>>>
>>> [kernel-doc] fix various DocBook build problems/warnings
>>>
>>> Most serious is fixing include/sound/pcm.h, which breaks the DocBook
>>> build.
>>
>>What is the error exactly? IIRC, it did work in the early version.
>>Well, I need to test it by myself...
>
>
> OK, I see it, too. How about the fix below, instead?
>
>
> [PATCH] Fix DocBook build in sound/pcm.h
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
>
> diff --git a/include/sound/pcm.h b/include/sound/pcm.h
> --- a/include/sound/pcm.h
> +++ b/include/sound/pcm.h
> @@ -910,7 +910,7 @@ int snd_pcm_format_big_endian(snd_pcm_fo
> * Returns 1 if the given PCM format is CPU-endian, 0 if
> * opposite, or a negative error code if endian not specified.
> */
> -/* int snd_pcm_format_cpu_endian(snd_pcm_format_t format); */
> +int snd_pcm_format_cpu_endian(snd_pcm_format_t format);
> #ifdef SNDRV_LITTLE_ENDIAN
> #define snd_pcm_format_cpu_endian snd_pcm_format_little_endian
> #else
I considered that, but decided not to, given the C pre-processor games
that are occurring with that symbol shortly after the commented-out block.
Jeff
next prev parent reply other threads:[~2005-09-07 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 5:17 [git patch] fix DocBook build Jeff Garzik
2005-09-07 10:00 ` Takashi Iwai
2005-09-07 10:12 ` Takashi Iwai
2005-09-07 11:27 ` Jeff Garzik [this message]
2005-09-07 12:17 ` 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=431ECEBA.7040802@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=torvalds@osdl.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 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.