linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@microsoft.com, kys@microsoft.com,
	haiyangz@microsoft.com, sthemmin@microsoft.com,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL v3] Hyper-V commits for 5.0
Date: Fri, 11 Jan 2019 10:15:52 +0100	[thread overview]
Message-ID: <20190111091552.GA16264@kroah.com> (raw)
In-Reply-To: <20190110152432.75529214C6@mail.kernel.org>

On Thu, Jan 10, 2019 at 10:24:31AM -0500, Sasha Levin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> 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)
> 
> - ----------------------------------------------------------------
> 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.
> 
> - ----------------------------------------------------------------

Did you really push out an updated tag?  I still get the following text
when doing a pull of this tag:

-----------
hyperv-fixes-signed
-----------

So it looks like nothing changed from your previous request.

Note, when creating the signed tag, with 'git tag -s' you have to enter
the text you want to show up in the tag into the editor at that time.

thanks,

greg k-h

  reply	other threads:[~2019-01-11  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 15:24 [GIT PULL v3] Hyper-V commits for 5.0 Sasha Levin
2019-01-11  9:15 ` Greg KH [this message]
2019-01-11 14:10   ` Sasha Levin
2019-01-11 14:30     ` 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=20190111091552.GA16264@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@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;
as well as URLs for NNTP newsgroup(s).