From: Rasesh Mody <rasesh.mody@qlogic.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Sony Chacko <sony.chacko@qlogic.com>
Subject: Re: [dpdk-dev] [PATCH 5/6] doc: Update BNX2X PMD documentation
Date: Thu, 22 Oct 2015 00:39:05 +0000 [thread overview]
Message-ID: <2552F74A0BCCBE4DBE2AD218C81B2811085E8982@avmb3.qlogic.org> (raw)
In-Reply-To: <1855137.XKbRK7D4tM@xps13>
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, October 20, 2015 9:20 AM
>
> This patch can be avoided by updating the documentation with each code
> change atomically.
Agreed, will take care in next submission.
________________________________
This message and any attached documents contain information from the sending company or its parent company(s), subsidiaries, divisions or branch offices that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
next prev parent reply other threads:[~2015-10-22 0:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 16:53 [dpdk-dev] [PATCH 0/6] bnx2x: Enable BNX2X PMD versioned at 1.0.0 Rasesh Mody
2015-10-08 16:54 ` [dpdk-dev] [PATCH 1/6] bnx2x: FreeBSD enablement Rasesh Mody
2015-10-08 16:54 ` [dpdk-dev] [PATCH 2/6] bnx2x: Linux 32bit enablement Rasesh Mody
2015-10-08 16:54 ` [dpdk-dev] [PATCH 3/6] maintainers: Add maintainers for BNX2X PMD Rasesh Mody
2015-10-08 16:54 ` [dpdk-dev] [PATCH 4/6] config: Enable BNX2X driver build by default Rasesh Mody
2015-10-20 16:18 ` Thomas Monjalon
2015-10-22 0:40 ` Rasesh Mody
2015-10-08 16:54 ` [dpdk-dev] [PATCH 5/6] doc: Update BNX2X PMD documentation Rasesh Mody
2015-10-20 16:19 ` Thomas Monjalon
2015-10-22 0:39 ` Rasesh Mody [this message]
2015-10-08 16:54 ` [dpdk-dev] [PATCH 6/6] bnx2x: Add BNX2X PMD versioning Rasesh Mody
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=2552F74A0BCCBE4DBE2AD218C81B2811085E8982@avmb3.qlogic.org \
--to=rasesh.mody@qlogic.com \
--cc=dev@dpdk.org \
--cc=sony.chacko@qlogic.com \
--cc=thomas.monjalon@6wind.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).