From: Jeff Garzik <jgarzik@pobox.com>
To: Martin Waitz <tali@admingilde.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/6] DocBook: changes and extensions to the kernel documentation
Date: Wed, 06 Apr 2005 16:06:38 -0400 [thread overview]
Message-ID: <4254414E.9010507@pobox.com> (raw)
In-Reply-To: <20050406114653.064745000@faui31y>
Martin Waitz wrote:
> --- linux-docbook.orig/drivers/video/fbmem.c 2005-04-06 12:13:12.674832161 +0200
> +++ linux-docbook/drivers/video/fbmem.c 2005-04-06 12:24:11.946113964 +0200
> @@ -1257,6 +1257,8 @@ int fb_new_modelist(struct fb_info *info
> static char *video_options[FB_MAX];
> static int ofonly;
>
> +extern const char *global_mode_option;
> +
> /**
> * fb_get_options - get kernel boot parameters
> * @name: framebuffer name as it would appear in
> @@ -1297,9 +1299,6 @@ int fb_get_options(char *name, char **op
> return retval;
> }
>
> -
> -extern const char *global_mode_option;
> -
> /**
> * video_setup - process command line options
> * @options: string of options
> Index: linux-docbook/include/linux/skbuff.h
> ===================================================================
> --- linux-docbook.orig/include/linux/skbuff.h 2005-04-06 12:13:12.677831708 +0200
> +++ linux-docbook/include/linux/skbuff.h 2005-04-06 12:24:11.954112753 +0200
> @@ -974,6 +974,7 @@ static inline void __skb_queue_purge(str
> kfree_skb(skb);
> }
>
> +#ifndef CONFIG_HAVE_ARCH_DEV_ALLOC_SKB
> /**
> * __dev_alloc_skb - allocate an skbuff for sending
> * @length: length to allocate
> @@ -986,7 +987,6 @@ static inline void __skb_queue_purge(str
> *
> * %NULL is returned in there is no free memory.
> */
> -#ifndef CONFIG_HAVE_ARCH_DEV_ALLOC_SKB
> static inline struct sk_buff *__dev_alloc_skb(unsigned int length,
> int gfp_mask)
> {
> Index: linux-docbook/mm/vmalloc.c
> ===================================================================
> --- linux-docbook.orig/mm/vmalloc.c 2005-04-06 12:13:12.680831254 +0200
> +++ linux-docbook/mm/vmalloc.c 2005-04-06 12:24:11.963111391 +0200
> @@ -475,6 +475,10 @@ void *vmalloc(unsigned long size)
>
> EXPORT_SYMBOL(vmalloc);
>
> +#ifndef PAGE_KERNEL_EXEC
> +# define PAGE_KERNEL_EXEC PAGE_KERNEL
> +#endif
> +
> /**
> * vmalloc_exec - allocate virtually contiguous, executable memory
> *
> @@ -488,10 +492,6 @@ EXPORT_SYMBOL(vmalloc);
> * use __vmalloc() instead.
> */
>
> -#ifndef PAGE_KERNEL_EXEC
> -# define PAGE_KERNEL_EXEC PAGE_KERNEL
> -#endif
> -
> void *vmalloc_exec(unsigned long size)
> {
> return __vmalloc(size, GFP_KERNEL | __GFP_HIGHMEM, PAGE_KERNEL_EXEC);
Although these patches do nothing but move code above a comment block,
they make me worry/grumble, because the author clearly preferred the
original code layout.
I'm -not- going to NAK this changeset, since it's not my code, but just
pointing this out. It would be nice if kernel-doc could grok this sort
of stuff, but I understand why it can't (without parsing c/cpp).
ACK for the other changesets in your series.
Jeff
next prev parent reply other threads:[~2005-04-06 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 11:46 [patch 0/6] DocBook updates Martin Waitz
2005-04-06 11:46 ` [patch 1/6] DocBook: changes and extensions to the kernel documentation Martin Waitz
2005-04-06 20:06 ` Jeff Garzik [this message]
2005-04-06 11:46 ` [patch 2/6] DocBook: fix <void/> xml tag Martin Waitz
2005-04-06 11:46 ` [patch 3/6] DocBook: fix some descriptions Martin Waitz
2005-04-06 11:46 ` [patch 4/6] DocBook: use <informalexample> for examples Martin Waitz
2005-04-06 11:46 ` [patch 5/6] DocBook: remove obsolete templates Martin Waitz
2005-04-06 11:46 ` [patch 6/6] DocBook: Use xmlto to process the DocBook files Martin Waitz
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=4254414E.9010507@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tali@admingilde.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