From: Simon Horman <horms@verge.net.au>
To: "Choi, David" <David.Choi@Micrel.Com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, "Li,
Charles" <Charles.Li@Micrel.Com>
Subject: Re: [PATCH v3 linux-2.6.35-rc3] ks8842 driver
Date: Tue, 13 Jul 2010 11:06:43 +0900 [thread overview]
Message-ID: <20100713020642.GH18341@verge.net.au> (raw)
In-Reply-To: <C43529A246480145B0A6D0234BDB0F0D481D72@MELANITE.micrel.com>
On Mon, Jul 12, 2010 at 05:11:40PM -0700, Choi, David wrote:
> Hi David & Simon and all,
>
>
>
> Thank you very much for your interests and comments for this patch.
>
>
>
> It seems that there are differences between Micrel ks8842 device and
> Timberdale FPGA based device
>
> with generic bus interface. In order to check the differences, I have
> sent several times but have not
>
> received any response. This patch is to support ks8841/ks8842 device
> from Micrel.
Hi David,
your mail client seems to have mangled your patches and is
providing an HTML version of the mail. I don't think this
was the case with the v2 patches. Did you change the
way that you are sending your email?
parent reply other threads:[~2010-07-13 2:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <C43529A246480145B0A6D0234BDB0F0D481D72@MELANITE.micrel.com>]
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=20100713020642.GH18341@verge.net.au \
--to=horms@verge.net.au \
--cc=Charles.Li@Micrel.Com \
--cc=David.Choi@Micrel.Com \
--cc=davem@davemloft.net \
--cc=netdev@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).