From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [00/37] Clean up duplicate includes
Date: Sun, 22 Jul 2007 08:00:41 +0530 [thread overview]
Message-ID: <a781481a0707211930l7e712dedo474a5e9e44e84adc@mail.gmail.com> (raw)
In-Reply-To: <200707211701.23911.jesper.juhl@gmail.com>
On 7/21/07, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> [...]
> These are the patches in this series :
Ok, I've reviewed all patches in this series except:
> [PATCH][12/37] Clean up duplicate includes in drivers/net/
> [PATCH][28/37] Clean up duplicate includes in net/ipv4/
> [PATCH][32/37] Clean up duplicate includes in net/sunrpc/
which I did not find anywhere ... not even on netdev@
Anyway, the entire series was OK, just removing a #include
line when that exact same header was already #include'd in
the same file. [ I also wonder if this patchset ends up exposing
some header-include-ordering problems that were previously
hidden, actually. ]
> Please consider applying these patches.
I think these are trivial and obvious enough -- can probably be
merged together into single patch by Andrew and just slammed
into the kernel tree :-)
Thanks,
Satyam
next prev parent reply other threads:[~2007-07-22 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 15:01 Jesper Juhl
2007-07-22 2:30 ` Satyam Sharma [this message]
2007-07-22 5:13 ` [00/37] Clean up duplicate includes (resend patch 12) Jesper Juhl
2007-07-22 5:13 ` [00/37] Clean up duplicate includes (resend patch 28) Jesper Juhl
2007-07-22 5:14 ` [00/37] Clean up duplicate includes (resend patch 32) Jesper Juhl
2007-07-22 6:38 ` [00/37] Clean up duplicate includes Satyam Sharma
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=a781481a0707211930l7e712dedo474a5e9e44e84adc@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jesper.juhl@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®