Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755258AbbHKFfq (ORCPT ); Tue, 11 Aug 2015 01:35:46 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:46375 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752601AbbHKFfp (ORCPT ); Tue, 11 Aug 2015 01:35:45 -0400 Date: Mon, 10 Aug 2015 22:35:42 -0700 (PDT) Message-Id: <20150810.223542.2033645138701106691.davem@davemloft.net> To: xiakaixu@huawei.com Cc: fengguang.wu@intel.com, ast@plumgrid.com, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, wangnan0@huawei.com Subject: Re: [PATCH net-next] bpf: fix the bug "'struct bpf_array' has no member named 'prog'" in s390 architecture From: David Miller In-Reply-To: <1439269224-13266-1-git-send-email-xiakaixu@huawei.com> References: <1439269224-13266-1-git-send-email-xiakaixu@huawei.com> X-Mailer: Mew version 6.6 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Mon, 10 Aug 2015 22:35:44 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 768 Lines: 18 From: Kaixu Xia Date: Tue, 11 Aug 2015 05:00:24 +0000 > 'Kbuild test robot' sent me an email about a build error > "'struct bpf_array' has no member named 'prog'" in s390 > architecture. This error is caused by commit: 2a36f0b92eb > 638dd023870574eb471b1c56be9ad [656/692] bpf: Make the bpf > _prog_array_map more generic. In this patch, the member 'prog' > of struct bpf_array has been replaced by 'ptrs'. So this > patch fix it. Please resubmit with a proper "Fixes: " and "Signed-off-by: " tags. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/