From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PULL 0/1] virtio-ccw: one more patch for 4.21
Date: Thu, 3 Jan 2019 11:50:22 -0500 [thread overview]
Message-ID: <20190103114955-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190103095507.7ef65472.cohuck@redhat.com>
On Thu, Jan 03, 2019 at 09:55:07AM +0100, Cornelia Huck wrote:
> On Wed, 19 Dec 2018 11:14:13 +0100
> Cornelia Huck <cohuck@redhat.com> wrote:
>
> > The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22:
> >
> > virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-ccw-20181219
> >
> > for you to fetch changes up to 6fb95ef30707f1b2fcaea8d6dc873055e0460b1a:
> >
> > virtio-ccw: diag 500 may return a negative cookie (2018-12-19 11:01:57 +0100)
> >
> > ----------------------------------------------------------------
> > One small documentation fix for 4.21.
> >
> > ----------------------------------------------------------------
> >
> > Cornelia Huck (1):
> > virtio-ccw: diag 500 may return a negative cookie
> >
> > Documentation/virtual/kvm/s390-diag.txt | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
>
> ping?
Sorry holidays :)
I'll pick this up for the next pull.
--
MST
next prev parent reply other threads:[~2019-01-03 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 10:14 [PULL 0/1] virtio-ccw: one more patch for 4.21 Cornelia Huck
2018-12-19 10:14 ` [PULL 1/1] virtio-ccw: diag 500 may return a negative cookie Cornelia Huck
2019-01-03 8:55 ` [PULL 0/1] virtio-ccw: one more patch for 4.21 Cornelia Huck
2019-01-03 16:50 ` Michael S. Tsirkin [this message]
2019-01-03 16:51 ` Michael S. Tsirkin
2019-01-04 9:56 ` Cornelia Huck
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=20190103114955-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).