All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Ceuleers <jan.ceuleers@computer.org>
To: Hayes Wang <hayeswang@realtek.com>
Cc: dwmw2@infradead.org, ben@decadent.org.uk, romieu@fr.zoreil.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: =? ?q?=5BPATCH=20firmware=203/4=5D=20rtl=5Fnic=3A=20add=20new=20firmware=20for=20RTL8106E?=
Date: Mon, 09 Jul 2012 12:33:24 +0200	[thread overview]
Message-ID: <4FFAB374.7040008@computer.org> (raw)
In-Reply-To: <1341803512-1309-3-git-send-email-hayeswang@realtek.com>

On 07/09/2012 05:11 AM, Hayes Wang wrote:
> File: rtl_nic/rtl8106e-1.fw
> Version: 0.0.1
> 
> Signed-off-by: Hayes Wang <hayeswang@realtek.com>

Hi

I'm afraid that the subject lines of patches 3/4 and 4/4 were mangled.
Could you try again?

Thanks, Jan

  reply	other threads:[~2012-07-09 10:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  3:11 [PATCH firmware 1/4] rtl_nic: update firmware for RTL8168F Hayes Wang
2012-07-09  3:11 ` [PATCH firmware 2/4] rtl_nic: update firmware for RTL8411 Hayes Wang
2012-07-09 23:58   ` Ben Hutchings
2012-07-09  3:11 ` =? ?q?=5BPATCH=20firmware=203/4=5D=20rtl=5Fnic=3A=20add=20new=20firmware=20for=20RTL8106E?= Hayes Wang
2012-07-09 10:33   ` Jan Ceuleers [this message]
2012-07-10  0:08   ` [PATCH firmware 3/4] rtl_nic: add new firmware for RTL8106E Ben Hutchings
2012-07-09  3:11 ` =? ?q?=5BPATCH=20firmware=204/4=5D=20rtl=5Fnic=3A=20add=20new=20firmware=20for=20RTL8168G?= Hayes Wang
2012-07-10  0:08   ` [PATCH firmware 4/4] rtl_nic: add new firmware for RTL8168G Ben Hutchings
2012-07-11 12:10     ` [PATCH firmware] rtl_nic: update " Hayes Wang
2012-07-19  0:59       ` Ben Hutchings
2012-07-09 23:58 ` [PATCH firmware 1/4] rtl_nic: update firmware for RTL8168F Ben Hutchings

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=4FFAB374.7040008@computer.org \
    --to=jan.ceuleers@computer.org \
    --cc=ben@decadent.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=hayeswang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.