From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.24; helo=mga09.intel.com; envelope-from=siyuan.fu@intel.com; receiver=edk2-devel@lists.01.org Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 56252220EE069 for ; Sun, 3 Dec 2017 17:49:22 -0800 (PST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Dec 2017 17:53:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,356,1508828400"; d="scan'208";a="9142634" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga003.jf.intel.com with ESMTP; 03 Dec 2017 17:53:51 -0800 Received: from fmsmsx153.amr.corp.intel.com (10.18.125.6) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 3 Dec 2017 17:53:50 -0800 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by FMSMSX153.amr.corp.intel.com (10.18.125.6) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 3 Dec 2017 17:53:50 -0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by shsmsx102.ccr.corp.intel.com ([169.254.2.175]) with mapi id 14.03.0319.002; Mon, 4 Dec 2017 09:53:49 +0800 From: "Fu, Siyuan" To: "Wu, Jiaxin" , "edk2-devel@lists.01.org" CC: "Ye, Ting" , Karunakar P Thread-Topic: [Patch 0/2] Check Media status before starting DHCP process. Thread-Index: AQHTan/Y8l66IEUHFkmk4of9r/uO9aMybx6g Date: Mon, 4 Dec 2017 01:53:49 +0000 Message-ID: References: <1512117526-11308-1-git-send-email-jiaxin.wu@intel.com> In-Reply-To: <1512117526-11308-1-git-send-email-jiaxin.wu@intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZTZiMTY3ZGYtMGU2Mi00NzVjLTg5OTctZGYyOTkzN2RkZGExIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiI1TEkrbEh5K3VqclwvRjg3a1hSR0dSRDRTTTRrXC9TNFQ5SGh4Zk5naXl5a0NCZDZqMWRhMWxEd1NNRG1VNTZQZFwvIn0= x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: [Patch 0/2] Check Media status before starting DHCP process. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2017 01:49:22 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Jiaxin If the network cable is plug-in after this error returned, will the IP/DHCP= driver restart DHCP process to request an address automatically? BestRegards Fu Siyuan > -----Original Message----- > From: Wu, Jiaxin > Sent: Friday, December 1, 2017 4:39 PM > To: edk2-devel@lists.01.org > Cc: Ye, Ting ; Fu, Siyuan ; > Karunakar P ; Wu, Jiaxin > Subject: [Patch 0/2] Check Media status before starting DHCP process. >=20 > Cc: Ye Ting > Cc: Fu Siyuan > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Karunakar P > Signed-off-by: Wu Jiaxin >=20 > Jiaxin Wu (2): > MdeModulePkg/Dhcp4Dxe: Check Media status before starting DHCP > process. > NetworkPkg/Dhcp6Dxe: Check Media status before starting DHCP process. >=20 > MdeModulePkg/Universal/Network/Dhcp4Dxe/Dhcp4Impl.c | 13 ++++++++++++- > NetworkPkg/Dhcp6Dxe/Dhcp6Impl.c | 14 +++++++++++++- > 2 files changed, 25 insertions(+), 2 deletions(-) >=20 > -- > 1.9.5.msysgit.1