From: Zhu Yi <yi.zhu@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] iwl3945 & iwl4965: mark more functions/variables static
Date: Thu, 18 Oct 2007 16:38:24 +0800 [thread overview]
Message-ID: <1192696704.3069.30.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20071018082635.GA10343@infradead.org>
On Thu, 2007-10-18 at 09:26 +0100, Christoph Hellwig wrote:
> ping.
Pong.
Sorry for the late response, I just come back from vacation. I'm looking
at your patches. Basically I agree with them. But I also have some other
patches pending. So I need to merge them together into one patch series
and send to the list ASAP.
Thanks,
-yi
next prev parent reply other threads:[~2007-10-18 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 12:32 [PATCH 1/3] iwl3945 & iwl4965: mark more functions/variables static Christoph Hellwig
2007-10-18 8:26 ` Christoph Hellwig
2007-10-18 8:38 ` Zhu Yi [this message]
2007-10-25 6:36 ` Zhu Yi
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=1192696704.3069.30.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).