[OE-core] [PATCH] iproute2 4.7.0 -> 4.9.0

Zheng, Ruoqin zhengrq.fnst at cn.fujitsu.com
Mon Jan 9 01:23:55 UTC 2017


I just refer to previous “iproute2-4.3.0-musl.patch” patch to produce this patch, So should I write Upstream-Status tag as same as last patch or merge iproute2-4.9.0-musl.patch to iproute2-4.3.0-musl.patch ?

Zheng

From: Burton, Ross [mailto:ross.burton at intel.com]
Sent: Saturday, January 07, 2017 1:12 AM
To: Zheng, Ruoqin/郑 若钦 <zhengrq.fnst at cn.fujitsu.com>
Cc: OE-core <openembedded-core at lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] iproute2 4.7.0 -> 4.9.0


On 26 December 2016 at 06:15, Zheng Ruoqin <zhengrq.fnst at cn.fujitsu.com<mailto:zhengrq.fnst at cn.fujitsu.com>> wrote:
+Subject: [PATCH] fix 4.9.0  musl compile problem
+
+Avoid in6_addr redefinition
+
+Signed-off-by: Zheng Ruoqin <zhengrq.fnst at cn.fujitsu.com<mailto:zhengrq.fnst at cn.fujitsu.com>>

This is missing an Upstream-Status tag.

Ross


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170109/455e3d6d/attachment-0002.html>


More information about the Openembedded-core mailing list