From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [GIT PULL] commits for Linux 4.15
Date: Mon, 9 Apr 2018 11:02:55 +0200 [thread overview]
Message-ID: <20180409090255.GA25664@kroah.com> (raw)
In-Reply-To: <DM5PR2101MB103240E900ABBBB4EA218181FBBB0@DM5PR2101MB1032.namprd21.prod.outlook.com>
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
>
> =====
>
>
> The following changes since commit df57458873da1a2a52e31c96cff43942c3557037:
>
> 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.git tags/for-greg-4.15-04052018
>
> for you to fetch changes up to e004aff712271a4528e4a1f7dc64d0dc8767a237:
>
> thermal: int3400_thermal: fix error handling in int3400_thermal_probe() (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 suspend
Let me drop it and see, if that fixes the build...
greg k-h
next prev parent reply other threads:[~2018-04-09 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 6:23 [GIT PULL] commits for Linux 4.15 Sasha Levin
2018-04-09 9:02 ` Greg KH [this message]
2018-04-09 9:31 ` Greg KH
2018-04-09 18:30 ` Sasha Levin
2018-04-10 13:22 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-04-15 21:37 Sasha Levin
2018-04-24 17:04 ` Greg KH
2018-03-19 15:38 Sasha Levin
2018-03-22 13:06 ` Greg KH
2018-03-15 22:40 Sasha Levin
2018-03-16 14:45 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180409090255.GA25664@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.