From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] driver/net: remove unnecessary macro for unused variables
Date: Mon, 15 May 2017 10:26:00 +0100 [thread overview]
Message-ID: <85a9aa4c-8748-6cba-95f2-6419f649d590@intel.com> (raw)
In-Reply-To: <20170515091942.GB3102@yliu-dev.sh.intel.com>
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.
Thanks,
ferruh
>
> --yliu
>
>> But postponing them most probably will mean rebasing these patches
>> later, so if this is not causing any problem for you, please let me know
>> so that I can get them earlier.
>>
>> Thanks,
>> ferruh
next prev parent reply other threads:[~2017-05-15 9:26 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 [this message]
2017-05-15 9:24 ` Yuanhan Liu
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=85a9aa4c-8748-6cba-95f2-6419f649d590@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=yuanhan.liu@linux.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).