From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI: cleanup scan.c whitespace & coding style
Date: Sat, 30 Jul 2005 12:35:34 +0200 [thread overview]
Message-ID: <20050730103534.GA26019@elf.ucw.cz> (raw)
In-Reply-To: <200507271630.58757.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Hi!
> Make whitespace/coding style consistent. No functional change (produces
> object code identical to pre-patch version).
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
>
>
> -static void acpi_device_release(struct kobject * kobj)
> +static void acpi_device_release (
> + struct kobject *kobj)
Pretty please, this is uglyer than original. See CodingStyle:
void fun(int a, int b, int c)
ACPI uses different codingstyle at places, but lets move to the
Doc*/CodingStyle direction.
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-30 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 22:30 ACPI: cleanup scan.c whitespace & coding style Bjorn Helgaas
[not found] ` <200507271630.58757.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-07-30 10:35 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-31 6:29 Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3004311E42-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-08-01 19:10 ` Bjorn Helgaas
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=20050730103534.GA26019@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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