kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Eric Farman <farman@linux.ibm.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PULL 0/1] one vfio-ccw patch for 5.6
Date: Mon, 10 Feb 2020 13:43:30 +0100	[thread overview]
Message-ID: <your-ad-here.call-01581338610-ext-6781@work.hours> (raw)
In-Reply-To: <20200206170331.1032-1-cohuck@redhat.com>

On Thu, Feb 06, 2020 at 06:03:30PM +0100, Cornelia Huck wrote:
> The following changes since commit d1eef1c619749b2a57e514a3fa67d9a516ffa919:
> 
>   Linux 5.5-rc2 (2019-12-15 15:16:08 -0800)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/vfio-ccw.git tags/vfio-ccw-20200206
> 
> for you to fetch changes up to dbaf10027ae92a66f0dfad33e1e3453daa16373f:
> 
>   vfio-ccw: Use the correct style for SPDX License Identifier (2020-01-07 10:37:34 +0100)
> 
> ----------------------------------------------------------------
> fix style of SPDX License Identifier
> 
> ----------------------------------------------------------------
> 
> Nishad Kamdar (1):
>   vfio-ccw: Use the correct style for SPDX License Identifier
> 
>  drivers/s390/cio/vfio_ccw_trace.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> -- 
> 2.21.1
> 
Pulled into fixes, thanks!


      parent reply	other threads:[~2020-02-10 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 17:03 [PULL 0/1] one vfio-ccw patch for 5.6 Cornelia Huck
2020-02-06 17:03 ` [PULL 1/1] vfio-ccw: Use the correct style for SPDX License Identifier Cornelia Huck
2020-02-10 12:43 ` Vasily Gorbik [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=your-ad-here.call-01581338610-ext-6781@work.hours \
    --to=gor@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.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).