From: ethan zhao <ethan.zhao@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: balbi@ti.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sriharsha.devdas@oracle.com,
ethan.kernel@gmail.com, vaughan.cao@oracle.com
Subject: Re: [PATCH NET-NEXT V2] netxen: fix ethtool rx_dropped information in ethtool get_ethtool_stats()
Date: Wed, 09 Jul 2014 13:15:13 +0800 [thread overview]
Message-ID: <53BCCFE1.5000806@oracle.com> (raw)
In-Reply-To: <20140708.204602.1475610247455018529.davem@davemloft.net>
David,
Sorry I don't know who owns this driver, the SOB of other patches
to netxen may mislead me you could ACK it or not, so it is definitely
not the original meaning that ask you specifically to review one patch.
just ask for help point to someone could review it.
Thanks,
Ethan
On 2014/7/9 11:46, David Miller wrote:
> From: ethan zhao<ethan.zhao@oracle.com>
> Date: Wed, 09 Jul 2014 10:41:23 +0800
>
>> Please help to review and confirm this patch.
> It's not in patchwork, therefore it's not in my queue.
>
> It is also not my responsibility to review all patches, that's
> a joint responsibility of everyone on this mailing list.
>
> So asking me specifically to review a patch is really not
> generally inappropriate.
>
> Thanks.
>
next prev parent reply other threads:[~2014-07-09 5:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1404827830-22990-1-git-send-email-ethan.zhao@oracle.com>
2014-07-09 2:41 ` [PATCH NET-NEXT V2] netxen: fix ethtool rx_dropped information in ethtool get_ethtool_stats() ethan zhao
2014-07-09 3:46 ` David Miller
2014-07-09 5:15 ` ethan zhao [this message]
2014-07-09 6:30 ` Shahed Shaikh
2014-07-09 6:35 ` Ethan Zhao
2014-07-09 11:32 ` Manish Chopra
2014-07-09 11:45 ` vaughan
2014-07-10 1:31 ` ethan zhao
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=53BCCFE1.5000806@oracle.com \
--to=ethan.zhao@oracle.com \
--cc=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=ethan.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sriharsha.devdas@oracle.com \
--cc=vaughan.cao@oracle.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 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).