From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@microsoft.com, kys@microsoft.com,
haiyangz@microsoft.com, sthemmin@microsoft.com,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL v2] Hyper-V commits for 5.0
Date: Thu, 10 Jan 2019 10:21:41 -0500 [thread overview]
Message-ID: <20190110152141.GN166797@sasha-vm> (raw)
In-Reply-To: <20190110074323.GB20273@kroah.com>
On Thu, Jan 10, 2019 at 08:43:23AM +0100, Greg KH wrote:
>On Thu, Jan 10, 2019 at 02:05:46AM -0500, Sasha Levin wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Hi Greg,
>>
>> Three bug fixes for different parts of the hyper-v code:
>>
>> - Fix for a lockup when changing NIC's MTU from Dexuan.
>> - Fix of use of uninitialized memory from Dexuan.
>> - Fix for memory corruption caused by ballooning from Vitaly.
>>
>> All 3 were tested internally.
>>
>> - --
>> Thanks,
>> Sasha
>>
>>
>> The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
>>
>> Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
>>
>> are available in the Git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-fixes-signed
>>
>> for you to fetch changes up to b5679cebf780c6f1c2451a73bf1842a4409840e7:
>>
>> vmbus: fix subchannel removal (2019-01-09 19:20:31 -0500)
>>
>> - ----------------------------------------------------------------
>> hyperv-fixes-signed
>>
>> - ----------------------------------------------------------------
>
>What changed? In the tag, the above "one line" message is all that is
>there, just like in the first version of this pull request.
>
>That's what I asked to be changed, please put the information you have
>above "Three bug...", in the tag itself.
>
>Then, when I do a 'git pull' I can see that in the changelog message and
>I do not have to go and manually cut/paste from the email, into the git
>commit terminal, the needed information.
>
>As it is, again, only the one line "hyperv-fixes-signed" shows up in the
>commit log when I want to do the pull.
>
>Try it yourself and see what I mean.
Ah, I see. Coming right up.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-01-10 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 7:05 [GIT PULL v2] Hyper-V commits for 5.0 Sasha Levin
2019-01-10 7:43 ` Greg KH
2019-01-10 15:21 ` Sasha Levin [this message]
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=20190110152141.GN166797@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sthemmin@microsoft.com \
/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