From: Jesper Juhl <jesper.juhl@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jesper Juhl <jesper.juhl@gmail.com>
Subject: [PATCH 0/3] Nuke a few duplicate includes
Date: Wed, 2 Jan 2008 03:39:00 +0100 [thread overview]
Message-ID: <200801020339.00698.jesper.juhl@gmail.com> (raw)
Including the same header twice (or more) in a .c file, outside any #ifdef's
and whatnot, serves no purpose except generating more work for the
compiler, so here are 3 patches that get rid of some pointless duplicate
includes.
Kind regards,
Jesper Juhl <jesper.juhl@gmail.com>
next reply other threads:[~2008-01-02 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 2:39 Jesper Juhl [this message]
2008-01-02 2:44 ` [PATCH 1/3] Nuke duplicate include from printk.c Jesper Juhl
2008-01-02 2:45 ` [PATCH 2/3] Nuke a duplicate include from profile.c Jesper Juhl
2008-01-02 2:46 ` [PATCH 3/3] Nuke duplicate header from sysctl.c Jesper Juhl
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=200801020339.00698.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome