All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Linux Kernel <linux-kernel@microsoft.com>
Subject: Re: [GIT PULL] commits for Linux 4.18
Date: Mon, 17 Sep 2018 13:27:04 +0200	[thread overview]
Message-ID: <20180917112704.GA28085@kroah.com> (raw)
In-Reply-To: <CY4PR21MB07760C514E414772E6187061FB190@CY4PR21MB0776.namprd21.prod.outlook.com>

On Fri, Sep 14, 2018 at 06:40:48PM +0000, Sasha Levin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi Greg,
> 
> Pleae pull commits for Linux 4.18 .
> 
> I've sent a review request for all commits over a week ago and all
> comments were addressed.

All 5 trees pulled in now, but I have dropped all of the ALSA
sparse-like fixes from the trees based on the review comments I made on
the 3.18.y patches.

thanks,

greg k-h

  reply	other threads:[~2018-09-17 16:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 18:40 [GIT PULL] commits for Linux 4.18 Sasha Levin
2018-09-17 11:27 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-12  3:26 Sasha Levin
2018-11-05 19:05 Sasha Levin
2018-10-22  9:13 Sasha Levin
2018-10-16 16:40 Sasha Levin
2018-10-18 15:18 ` Greg KH
2018-10-12 14:36 Sasha Levin
2018-10-16 10:54 ` Greg KH
2018-10-08 15:02 Sasha Levin
2018-10-08 17:10 ` Greg KH
     [not found] <5bb656f2.1c69fb81.ef8db.8483SMTPIN_ADDED_MISSING@mx.google.com>
2018-10-04 20:24 ` Greg KH
2018-10-02  0:58 Sasha Levin
2018-10-02 12:04 ` Greg KH
2018-09-28  0:26 Sasha Levin
2018-09-29 12:07 ` Greg KH
2018-10-01  0:49   ` Sasha Levin
2018-09-28  0:25 Sasha Levin
2018-09-24  1:01 Sasha Levin
2018-09-24  7:47 ` Greg KH
2018-09-17 23:46 Sasha Levin
2018-09-21 12:01 ` Greg KH
2018-09-10 14:28 Sasha Levin
2018-09-11 14:44 ` 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=20180917112704.GA28085@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Alexander.Levin@microsoft.com \
    --cc=linux-kernel@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.