Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp1347196pxu; Fri, 27 Nov 2020 05:27:34 -0800 (PST) X-Google-Smtp-Source: ABdhPJwT5dxFfL0n3TQG80aEAD7mnTgxihzM43WXEZbT4EjqNS6HNu0ESz+HbdDd3po/XfvWHBSE X-Received: by 2002:a05:6402:150b:: with SMTP id f11mr7613039edw.332.1606483654615; Fri, 27 Nov 2020 05:27:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606483654; cv=none; d=google.com; s=arc-20160816; b=qlrybUsiDqjLHrIg8x6WcFBj24NWr14uSOY66jpZL17HnmGIUs9ejDjuQf8JQOIst5 jD1Xwxx+1DwG2/9pSUy+SNFewNJin0eMyW6NfKTTFv51torHJDcrnbNAGfyRputJotbi Dd+XJ1YEoNV2MoWZx/0XWmslOnNB6H9fgUpF70I1VKGKP/oAbNYWSaZh4TAm5pKIrrjq wkjIkgpaVwp5k+/CjoweUlw9DmbL+hhIY0SyM/p+eYUzXHb3vOXM5NUZhP5UOrWqolQD iK4u3CGl3+YSro0YJi9PU+N4lXlEHF6t4puY0FiyZUkb4N3qB0NOlpj0eFb/eCQm3NBU LHdQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=38/wbfCKXTkC5LG04Smdt4//3XSDcNSerBfnYChVnqk=; b=UtkOrbiKh+m8OPJnqQMPgAeG2Pr5dVLv67nEGpmztyZbwfYkdS0MA0zssmguOtaQWv T/wXuJIvbc6GhwlajMypG9JZx2avg8V8JolwvXVL16grfeBmAmFjQQjbKPZ4RIYJbzDs O9KXGoNP6ntH1UIn3RIUbYPGiuFNpZ8OmDlHf6Fd+uDnhVOIuBZ0N3JKgF+nNNGvALIT 9CGpIMsCh1JTu/H+Vpg4whVZVoGqd68DDJAbI4fNLJMWju314LzrJ/ygeOyne+gQGIXb rSmq/xPkctYQAZ0FZfZciOrJXuxPITGUNPkRWoLMhYESKE0WOjaapBoBAU7IUULpPLuE kF4w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm2 header.b=A3RucOtO; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=Mks2GYvx; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cf17si4929688ejb.541.2020.11.27.05.26.59; Fri, 27 Nov 2020 05:27:34 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm2 header.b=A3RucOtO; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=Mks2GYvx; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730526AbgK0NWx (ORCPT + 99 others); Fri, 27 Nov 2020 08:22:53 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:50953 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729888AbgK0NWx (ORCPT ); Fri, 27 Nov 2020 08:22:53 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 11F685C00ED; Fri, 27 Nov 2020 08:22:52 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 27 Nov 2020 08:22:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=38/wbfCKXTkC5LG04Smdt4//3XS DcNSerBfnYChVnqk=; b=A3RucOtO4sfSGAUx8aw1p7nKrHNOxMH7C8353ibvzzk IqulggrIQkRE8iDVxFAFnwjOjgg7mMi7GTf0fVMmarE/tOon69N+5QCxfhDiWlDR zStrayoisgxXhDiKzr54pdmJqXxJ1n8DLRXVsWioMbTWggPk47sbdUa5tqcNV825 QOOMjt0IVAbH+I6bMoKdkbHUJPRTvZtS+2+4bR65tJAAFTT1RYbbfaXeLoNJY9Gl 1PZGffggoVa+dPmRvUAszb784Z1z3YdESxBkzkfeGe7inu60Cm7DfghMQa6ZBVfo 9Tw+vtrAxILFI70IfrE7dMxzbWuUj46s0jLH0fdwYIA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=38/wbf CKXTkC5LG04Smdt4//3XSDcNSerBfnYChVnqk=; b=Mks2GYvxs5dd/960MLWXxZ /TspEnhB6/8ioZsH7iCNFWBczpUkdeFRpNJuKpwFwKZj0RshbtSJqVwzHskoZ4CH oSUUVa0Q8d97mVt28Fo5GkktKkfosufs6v28/DtYsmTpk17BNl7szsMggLJwrAlg 75hvJlmpjP3Ui/fXvpaHY1X9sYx2gjpf/TRQYS1I6BqbopPVEjCl9WJZ+Tf7zxt8 o2tkdCrZ442pPbGnxBezvnEZf2Thp42HIAfa7I2ToU8HofvbaC5uew3J8S4gzT5M DUcKc4BNls9hRe7PeATEWZcwSbo/tiEzoRbHW1pXX0djyKaG765FGih/N6HXYwBw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudehgedghedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeeuleeltd ehkeeltefhleduuddvhfffuedvffduveegheekgeeiffevheegfeetgfenucffohhmrghi nhepkhgvrhhnvghlrdhorhhgnecukfhppeekvddrvddujedrvddtrddukeehnecuvehluh hsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhho rghhrdgtohhm X-ME-Proxy: Received: from localhost (82-217-20-185.cable.dynamic.v4.ziggo.nl [82.217.20.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 6E2E23064AB0; Fri, 27 Nov 2020 08:22:51 -0500 (EST) Date: Fri, 27 Nov 2020 14:22:49 +0100 From: Greg KH To: Hauke Mehrtens Cc: stable , Johannes Berg , linux-wireless@vger.kernel.org Subject: Re: stable backport of "wireless: Use linux/stddef.h instead of stddef.h" Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, Nov 27, 2020 at 12:04:00AM +0100, Hauke Mehrtens wrote: > Hi, > > Please backport "wireless: Use linux/stddef.h instead of stddef.h" to kernel > 4.14, 4.19 and 5.4. > This is upstream commit id 1b9ae0c92925ac40489be526d67d0010d0724ce0 > https://git.kernel.org/linus/1b9ae0c92925ac40489be526d67d0010d0724ce0 > > commit 1b9ae0c92925ac40489be526d67d0010d0724ce0 > Author: Hauke Mehrtens > Date: Thu May 21 22:14:22 2020 +0200 > > wireless: Use linux/stddef.h instead of stddef.h > > This patch fixes a build problem in broken build environments which was > introduced with 6989310f5d43 ("wireless: Use offsetof instead of custom > macro.") which was backported to the listed kernel versions. > > When the include path is fully correct you should not hit this problem, but > I got it because of some bug in by build system and also someone else > reported a similar problem to me and requested this backport. Now queued up, thanks. greg k-h