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.14
Date: Mon, 30 Apr 2018 06:02:19 -0700 [thread overview]
Message-ID: <20180430130219.GA10505@kroah.com> (raw)
In-Reply-To: <DM5PR2101MB103239F3196A8382D20D714EFB8D0@DM5PR2101MB1032.namprd21.prod.outlook.com>
On Fri, Apr 27, 2018 at 02:00:53AM +0000, Sasha Levin 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 d6949f48093c2d862d9bc39a7a89f2825c55edc4:
>
> Linux 4.14.36 (2018-04-24 09:36:40 +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.14-26042018
Did you really regenerate this tree? It has a load of patches that are
already upstream. I'm getting a bunch of conflicts when first trying to
merge, and then rebase it.
Can you verify this is the correct tag?
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-30 13:02 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 2:00 [GIT PULL] commits for Linux 4.14 Sasha Levin
2018-04-30 13:02 ` Greg KH [this message]
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
-- 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-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-12 0:58 alexander.levin
2017-12-12 11:50 ` 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=20180430130219.GA10505@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.