From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [GIT PULL] commits for Linux 4.4
Date: Thu, 5 Jul 2018 19:09:34 +0000 [thread overview]
Message-ID: <20180705190933.GL3776@sasha-vm> (raw)
In-Reply-To: <20180705181837.GA13468@kroah.com>
On Thu, Jul 05, 2018 at 08:18:37PM +0200, Greg KH wrote:
>On Thu, Jun 21, 2018 at 02:37:26AM +0000, Sasha Levin wrote:
>> Hi Greg,
>>
>> Pleae pull commits for Linux 4.4 .
>>
>> 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 dc45cafe612ec6960fe728f3260a0b751c73f4aa:
>>
>> Linux 4.4.136 (2018-06-06 16:46:24 +0200)
>>
>> are available in the Git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git tags/for-greg-4.4-20062018
>
>Same here, after rebasing, is this branch empty?
Hm, looks like it, I guess I had some overlap in the last 2 pull
requests I sent you. This one was supposed to wrap out v4.16..v4.17.
next prev parent reply other threads:[~2018-07-05 19:09 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 2:37 [GIT PULL] commits for Linux 4.4 Sasha Levin
2018-07-05 18:18 ` Greg KH
2018-07-05 19:09 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-12 3:26 Sasha Levin
2018-11-05 19:09 Sasha Levin
2018-10-22 9:14 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-28 14:12 ` Greg KH
2018-08-10 0:23 Sasha Levin
2018-08-22 8:37 ` Greg KH
2018-07-28 1:46 Sasha Levin
2018-07-28 10:28 ` Greg KH
2018-06-07 1:07 Sasha Levin
2018-06-05 4:00 Sasha Levin
2018-05-19 16:59 Sasha Levin
2018-05-28 8:04 ` Greg KH
2018-04-27 2:01 Sasha Levin
2018-04-27 4:50 ` Nathan Chancellor
2018-04-27 7:05 ` Greg KH
2018-04-27 7:35 ` Nathan Chancellor
2018-04-27 8:40 ` Timur Tabi
2018-04-27 18:04 ` Nathan Chancellor
2018-04-30 17:21 ` Bjorn Andersson
2018-04-30 17:34 ` Nathan Chancellor
2018-04-30 18:01 ` Bjorn Andersson
2018-04-27 8:15 ` Harsh Shandilya
2018-05-02 20:09 ` Greg KH
2018-05-03 6:23 ` Amit Pundir
2018-05-03 12:00 ` Greg KH
2018-05-03 6:49 ` Amit Pundir
2018-05-03 15:51 ` Greg KH
2018-05-03 15:51 ` Greg KH
2018-04-15 21:38 Sasha Levin
2018-04-24 17:03 ` Greg KH
2018-04-05 6:24 Sasha Levin
2018-04-10 8:50 ` Greg KH
2018-03-19 15:38 Sasha Levin
2018-03-22 14:11 ` Greg KH
2018-03-15 22:40 Sasha Levin
2018-03-19 9:09 ` Greg KH
2018-02-25 0:59 Sasha Levin
2018-02-28 15:20 ` Greg KH
2018-02-04 16:03 Sasha Levin
2018-02-23 10:59 ` Greg KH
2018-01-28 22:32 Sasha Levin
2017-12-20 15:37 alexander.levin
2017-12-21 9:51 ` Greg KH
2017-12-14 16:13 alexander.levin
2017-12-18 14:01 ` Greg KH
2017-12-12 0:59 alexander.levin
2017-12-12 12:45 ` Greg KH
2017-12-02 15:45 alexander.levin
2017-12-06 16:31 ` Greg KH
2017-11-30 22:02 alexander.levin
2017-11-30 22:01 alexander.levin
2017-11-24 17:14 alexander.levin
2017-11-28 9:57 ` Greg KH
2017-11-19 0:51 alexander.levin
2017-11-19 11:05 ` Greg KH
2017-11-08 20:45 Levin, Alexander (Sasha Levin)
2017-11-09 17:26 ` Greg KH
2017-10-25 1:39 Levin, Alexander (Sasha Levin)
2017-11-06 9:25 ` 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=20180705190933.GL3776@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox