From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] driver/net: remove unnecessary macro for unused variables
Date: Mon, 15 May 2017 17:24:45 +0800 [thread overview]
Message-ID: <20170515092445.GC3102@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <85a9aa4c-8748-6cba-95f2-6419f649d590@intel.com>
On Mon, May 15, 2017 at 10:26:00AM +0100, Ferruh Yigit wrote:
> On 5/15/2017 10:19 AM, Yuanhan Liu wrote:
> > On Mon, May 15, 2017 at 10:17:43AM +0100, Ferruh Yigit wrote:
> >> On 5/12/2017 11:33 AM, Ferruh Yigit wrote:
> >>> remove __rte_unused instances that are not required.
> >>>
> >>
> >> Hi Yuanhan,
> >>
> >> Does this kind of refactoring patches, specially the ones covering
> >> multiple drivers, cause trouble (more conflicts) to you while getting
> >> patches for stable trees?
> >
> > Yes, it's likely.
> >
> >> If so, I can postpone them through the end of integration deadline.
> >
> > I don't think it's necessary though. If a conflict happens, I will ask
> > the author to do backport :)
>
> OK, thanks for clarifying ...
>
> So, result is, refactoring patches won't be pushed through end of the
> release.
Yes, I see no strong need for that.
--yliu
prev parent reply other threads:[~2017-05-15 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 10:33 Ferruh Yigit
2017-05-12 11:39 ` Legacy, Allain
2017-05-15 0:53 ` Lu, Wenzhuo
2017-05-15 10:33 ` Ferruh Yigit
2017-05-15 2:31 ` Yuanhan Liu
2017-05-15 8:42 ` Ferruh Yigit
2017-05-15 9:17 ` Ferruh Yigit
2017-05-15 9:19 ` Yuanhan Liu
2017-05-15 9:26 ` Ferruh Yigit
2017-05-15 9:24 ` Yuanhan Liu [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=20170515092445.GC3102@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).