Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932579AbbHKSt5 (ORCPT ); Tue, 11 Aug 2015 14:49:57 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:50915 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752514AbbHKStz (ORCPT ); Tue, 11 Aug 2015 14:49:55 -0400 Date: Tue, 11 Aug 2015 11:49:54 -0700 (PDT) Message-Id: <20150811.114954.2113934998531402950.davem@davemloft.net> To: xiakaixu@huawei.com Cc: daniel@iogearbox.net, 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 v3 net-next] bpf: s390: Fix build error caused by the struct bpf_array member name changed From: David Miller In-Reply-To: <1439283411-163308-1-git-send-email-xiakaixu@huawei.com> References: <1439283411-163308-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]); Tue, 11 Aug 2015 11:49:55 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 769 Lines: 18 From: Kaixu Xia Date: Tue, 11 Aug 2015 08:56:51 +0000 > There is a build error that "'struct bpf_array' has no member > named 'prog'" on s390. In commit 2a36f0b92eb6 ("bpf: Make the > bpf_prog_array_map more generic"), the member 'prog' of struct > bpf_array is replaced by 'ptrs'. So this patch fixes it. > > Fixes: 2a36f0b92eb6 ("bpf: Make the bpf_prog_array_map more generic") > Reported-by: Wu Fengguang > Signed-off-by: Kaixu Xia Applied, thanks. -- 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/