From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: jbradford@dial.pipex.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stupid luser question
Date: Tue, 1 Oct 2002 20:30:44 +0200 [thread overview]
Message-ID: <3624A9D2016@vcnet.vc.cvut.cz> (raw)
On 1 Oct 02 at 19:14, jbradford@dial.pipex.com wrote:
> Just wondering, what is the purpose of the comment /* { */ which is found in various seemingly random places in the kernel:
>
> # grep -F -r "/* { */" *
>
> drivers/video/font_acorn_8x8.c:/* 7B */ 0x0C, 0x18, 0x18, 0x70, 0x18, 0x18, 0x0C, 0x00, /* { */
Body of character "{"...
> drivers/scsi/scsi_syms.c:#if defined(CONFIG_SCSI_LOGGING) /* { */
> drivers/scsi/scsi.c:#ifdef CONFIG_SCSI_LOGGING /* { */
> drivers/scsi/scsi.c:#ifdef CONFIG_SCSI_LOGGING /* { */
> drivers/message/fusion/mptbase.h:#ifdef __KERNEL__ /* { */
> drivers/message/fusion/mptscsih.c:#ifndef MPT_SCSI_USE_NEW_EH /* { */
> drivers/message/fusion/mptscsih.c:#ifdef MPT_SCSI_USE_NEW_EH /* { */
> drivers/message/fusion/mptscsih.c:#if 0 /* { */
> drivers/message/fusion/mptbase.c:#ifdef CONFIG_PROC_FS /* { */
All these are for cooperation with editors which find matching
brace/bracket/... for you:
#ifdef __KERNEL__ /* { */
...
#endif /* } __KERNEL__ */
and then you can quickly jump from ifdef to endif and back even in
editor which does not know about #if/ifdef/else/elif/ifndef/endif...
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-10-01 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 18:30 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 18:36 Stupid luser question John Hall
2002-10-01 18:14 jbradford
2002-10-01 18:29 ` Eli Carter
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=3624A9D2016@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.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.