From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-bl2nam02on0097.outbound.protection.outlook.com ([104.47.38.97]:22814 "EHLO NAM02-BL2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753201AbeDISa1 (ORCPT ); Mon, 9 Apr 2018 14:30:27 -0400 From: Sasha Levin To: Greg KH CC: "stable@vger.kernel.org" Subject: Re: [GIT PULL] commits for Linux 4.15 Date: Mon, 9 Apr 2018 18:30:25 +0000 Message-ID: <20180409183023.GF2341@sasha-vm> References: <20180409090255.GA25664@kroah.com> <20180409093106.GB3398@kroah.com> In-Reply-To: <20180409093106.GB3398@kroah.com> Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: stable-owner@vger.kernel.org List-ID: On Mon, Apr 09, 2018 at 11:31:06AM +0200, Greg KH wrote: >On Mon, Apr 09, 2018 at 11:02:55AM +0200, Greg KH wrote: >> On Thu, Apr 05, 2018 at 06:23:51AM +0000, Sasha Levin wrote: >> > Hi Greg, >> > >> > Pleae pull commits for Linux 4.15 . >> > >> > I've sent a review request for all commits over a week ago and all >> > comments were addressed. >> > >> > >> > Thanks, >> > Sasha >> > >> > =3D=3D=3D=3D=3D >> > >> > >> > The following changes since commit df57458873da1a2a52e31c96cff43942c35= 57037: >> > >> > Linux 4.15.10 (2018-03-15 10:57:00 +0100) >> > >> > are available in the Git repository at: >> > >> > git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.gi= t tags/for-greg-4.15-04052018 >> > >> > for you to fetch changes up to e004aff712271a4528e4a1f7dc64d0dc8767a23= 7: >> > >> > thermal: int3400_thermal: fix error handling in int3400_thermal_prob= e() (2018-04-05 00:52:24 -0400) >> >> I get a build error with this tree: >> >> ERROR: "pm_mutex" [drivers/scsi/scsi_transport_spi.ko] undefined! >> >> I'm guessing due to this patch: >> >> > Bart Van Assche (1): >> > block, scsi: Fix race between SPI domain validation and system s= uspend >> >> Let me drop it and see, if that fixes the build... > >Yes, that solved it, so I'm dropping this patch. How did you test build >this? I got the failure on a "simple" 'allmodconfig' x86 build. I see what went wrong; my scripts handled this scenario all wrong. It's a combination of allyesconfig building proerly, and my failure to parse modpost errors right. Now fixed, sorry! :(=