From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pf0-f194.google.com ([209.85.192.194]:33562 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751773AbdFHOTN (ORCPT ); Thu, 8 Jun 2017 10:19:13 -0400 Received: by mail-pf0-f194.google.com with SMTP id f27so5299333pfe.0 for ; Thu, 08 Jun 2017 07:19:13 -0700 (PDT) Received: from ubuntu.windy (c122-106-153-7.carlnfd1.nsw.optusnet.com.au. [122.106.153.7]) by smtp.gmail.com with ESMTPSA id q194sm9964112pfq.56.2017.06.08.07.19.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jun 2017 07:19:11 -0700 (PDT) Date: Fri, 9 Jun 2017 00:19:28 +1000 From: Vincent McIntyre To: linux-media@vger.kernel.org Subject: Re: [media_build] regression at 3a17e11 "update v4.10_sched_signal.patch" Message-ID: <20170608141926.GA16444@ubuntu.windy> References: <20170608131339.GA11167@ubuntu.windy> <20170608132826.GB11167@ubuntu.windy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170608132826.GB11167@ubuntu.windy> Sender: linux-media-owner@vger.kernel.org List-ID: > > $ cat drivers/media/rc/lirc_dev.c.rej > --- drivers/media/rc/lirc_dev.c > +++ drivers/media/rc/lirc_dev.c > @@ -18,7 +18,7 @@ > #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt > > #include > -#include > +#include > #include > #include > #include > A bit of staring brings this to light: The file that is being patched has extra lines relative to the patch 18 #undef pr_fmt 19 #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt 20 21 #include ** 22 #include 23 #include ** 24 #include 25 #include 26 #include 27 #include 28 #include 29 #include 30 #include This hunk applies cleanly, and seems to match up with recent kernel code (eg 174cd4b1e5fbd0d74c68cf3a74f5bd4923485512 sched/headers: Prepare to move signal wakeup & sigpending methods from into ) @@ -20,7 +20,7 @@ #include #include -#include +#include #include #include #include HTH Vince