From: Rasesh Mody <rasesh.mody@qlogic.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Dept-Eng DPDK Dev <Dept-EngDPDKDev@qlogic.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] qede: rename config option
Date: Fri, 3 Jun 2016 15:54:03 +0000 [thread overview]
Message-ID: <BY1PR11MB0151D7137AA3803EDEA8305385590@BY1PR11MB0151.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20160603150151.GA6808@bricha3-MOBL3>
Thanks!
> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Friday, June 03, 2016 8:02 AM
>
> 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
prev parent reply other threads:[~2016-06-03 15:54 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
2016-06-03 15:54 ` Rasesh Mody [this message]
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=BY1PR11MB0151D7137AA3803EDEA8305385590@BY1PR11MB0151.namprd11.prod.outlook.com \
--to=rasesh.mody@qlogic.com \
--cc=Dept-EngDPDKDev@qlogic.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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).