From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Alchemy: kill useless #include's, #define's and extern's (take 3)
Date: Wed, 16 Apr 2008 22:54:10 +0400 [thread overview]
Message-ID: <48064B52.4050804@ru.mvista.com> (raw)
In-Reply-To: <20080416172737.GA32263@linux-mips.org>
Ralf Baechle wrote:
>>Go thru the Alchemy code and hunt down every unneeded #include, #define, and
>>extern (some of which refer to already long dead functions).
>>Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>>---
>>Killed #include <au1xxx_dbdma.h> and couple #define's in
>>arch/mips/au1000/pb1200/board_setup.c...
>>Please update the queued patch, hopefully the last time. :-)
> Done,
Thanks. But actually, summary and description also did change -- but not
in the queue. :-)
> Ralf
WBR, Sergei
next prev parent reply other threads:[~2008-04-16 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 17:15 [PATCH] Alchemy: kill useless #include's, #define's and extern's (take 3) Sergei Shtylyov
2008-04-16 17:27 ` Ralf Baechle
2008-04-16 18:54 ` Sergei Shtylyov [this message]
2008-04-17 9:51 ` Ralf Baechle
2008-04-16 20:05 ` Jens Seidel
2008-04-17 11:34 ` Sergei Shtylyov
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=48064B52.4050804@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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