All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: alexander.levin@verizon.com
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [GIT PULL] commits for Linux 4.14
Date: Tue, 12 Dec 2017 12:50:45 +0100	[thread overview]
Message-ID: <20171212115045.GC23534@kroah.com> (raw)
In-Reply-To: <4e2e4527aa1f462fa52d769aa761af38@OMZP1LUMXCA17.uswin.ad.vzwcorp.com>

On Tue, Dec 12, 2017 at 12:58:56AM +0000, alexander.levin@verizon.com wrote:
> Hi Greg,
> 
> Pleae pull commits for Linux 4.14 .
> 
> 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 64138f0adb25ca8f34baa57af33260b05efe2874:
> 
>   Linux 4.14.5 (2017-12-10 13:40:45 +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.14-11122017
> 

Note, I've dropped the patches from this series that are already in
Dave's stable networking patch queue, as I'd prefer to take them from
him when he tests and sends them to me.

Otherwise, the rest are now queued up, thanks.

greg k-h

  reply	other threads:[~2017-12-12 11:50 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12  0:58 [GIT PULL] commits for Linux 4.14 alexander.levin
2017-12-12 11:50 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-12  3:26 Sasha Levin
2018-11-05 19:06 Sasha Levin
2018-10-22  9:13 Sasha Levin
2018-10-16 16:40 Sasha Levin
2018-10-12 14:36 Sasha Levin
2018-10-08 15:02 Sasha Levin
2018-10-02  0:58 Sasha Levin
2018-09-28  0:26 Sasha Levin
2018-09-24  1:01 Sasha Levin
2018-09-17 23:46 Sasha Levin
2018-09-14 18:41 Sasha Levin
2018-09-10 14:28 Sasha Levin
2018-08-25 15:10 Sasha Levin
2018-08-26  7:14 ` Greg KH
2018-08-10  0:23 Sasha Levin
2018-08-22  8:06 ` Greg KH
2018-07-28  1:46 Sasha Levin
2018-07-28 10:08 ` Greg KH
2018-06-21  2:36 Sasha Levin
2018-07-05 18:17 ` Greg KH
2018-06-07  1:07 Sasha Levin
2018-06-08  0:55 ` Eddie Chapman
2018-06-08  4:49   ` Greg KH
2018-06-05  4:00 Sasha Levin
2018-05-19 16:59 Sasha Levin
2018-05-27 15:36 ` Greg KH
2018-04-27  2:00 Sasha Levin
2018-04-30 13:02 ` Greg KH
2018-04-30 14:39   ` Sasha Levin
2018-04-30 15:06     ` Greg KH
2018-04-30 17:54       ` Sasha Levin
2018-04-30 18:28         ` Greg KH
2018-04-30 19:26           ` Greg KH
2018-05-02 16:53           ` Greg KH
2018-05-02 23:19 ` Greg KH
2018-05-02 23:36   ` Greg KH
2018-05-02 23:39     ` Sasha Levin
2018-05-03 12:02       ` Greg KH
2018-05-03 12:05         ` Greg KH
2018-04-23 19:54 Sasha Levin
2018-04-24  7:28 ` Greg KH
2018-04-15 21:37 Sasha Levin
2018-04-24 15:00 ` Greg KH
2018-04-05  6:24 Sasha Levin
2018-04-09 12:04 ` Greg KH
2018-03-19 15:38 Sasha Levin
2018-03-22 13:33 ` Greg KH
2018-03-15 22:40 Sasha Levin
2018-03-16 14:45 ` Greg KH
2018-02-25  0:59 Sasha Levin
2018-02-28 15:25 ` Greg KH
2018-02-04 16:03 Sasha Levin
2018-02-15 15:30 ` Greg KH
2018-02-15 19:36   ` Sasha Levin
2018-02-23 10:47     ` Greg KH
2018-02-23 11:10       ` Greg KH
2018-01-28 22:32 Sasha Levin
2018-02-04 10:47 ` Greg KH
2017-12-20 15:37 alexander.levin
2017-12-20 17:21 ` Greg KH
2017-12-14 16:13 alexander.levin
2017-12-18 13:09 ` Greg KH
2017-12-02 15:45 alexander.levin
2017-12-06 18:37 ` Greg KH
2017-11-30 22:02 alexander.levin

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=20171212115045.GC23534@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.levin@verizon.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.