DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Rasesh Mody <rasesh.mody@qlogic.com>
Cc: dev@dpdk.org, Dept-EngDPDKDev@qlogic.com
Subject: Re: [dpdk-dev] [PATCH 1/2] qede: rename config option
Date: Fri, 3 Jun 2016 16:01:52 +0100	[thread overview]
Message-ID: <20160603150151.GA6808@bricha3-MOBL3> (raw)
In-Reply-To: <20160530143841.GB24092@bricha3-MOBL3>

On Mon, May 30, 2016 at 03:38:41PM +0100, Bruce Richardson wrote:
> On Fri, May 06, 2016 at 09:21:30PM -0700, Rasesh Mody wrote:
> > Rename RTE_LIBRTE_QEDE_DEBUG_DRV to RTE_LIBRTE_QEDE_DEBUG_DRIVER
> > 
> > Fixes: 425cba2a5176 ("qede: enable PMD build")
> > Fixes: 33e9ff1b72ca ("qede: add core driver")
> > 
> These fixes lines don't have the correct commit id's in them. The commit
> "qede: enable PMD build" is actually commit 3eae93a9, and "qede: add core
> driver" is 2ea6f76a. The commit id of a patch can change from what it is
> originally when the patch is applied.
> 
> /Bruce
> 
Patch series applied to dpdk-next-net/rel_16_07 with corrected commit ids in
the fixes line, and some reworking of titles and commit messages as discussed.

Regards,
/Bruce

  reply	other threads:[~2016-06-03 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07  4:21 Rasesh Mody
2016-05-07  4:21 ` [dpdk-dev] [PATCH 2/2] qede: return LAN stats to MFW Rasesh Mody
2016-05-30 14:34   ` Bruce Richardson
2016-05-31 19:21     ` Harish Patil
2016-06-01  9:43       ` Thomas Monjalon
2016-06-01 14:16         ` Harish Patil
2016-06-01 14:31           ` Richardson, Bruce
2016-06-01 14:33             ` Harish Patil
2016-05-30 14:38 ` [dpdk-dev] [PATCH 1/2] qede: rename config option Bruce Richardson
2016-06-03 15:01   ` Bruce Richardson [this message]
2016-06-03 15:54     ` 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=20160603150151.GA6808@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=Dept-EngDPDKDev@qlogic.com \
    --cc=dev@dpdk.org \
    --cc=rasesh.mody@qlogic.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).