All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	linux-next <linux-next@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: kvms390 tree for Linux next
Date: Thu, 22 Jan 2015 14:36:16 +0100	[thread overview]
Message-ID: <54C0FCD0.7080108@de.ibm.com> (raw)

Stephen,

can you add the kvms390 tree at

git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git next

to linux-next?

This tree will almost always be merged via the kvm tree, but it helps us anyway detecting broken things before I ask Paolo to pull.

Thanks a lot for your work on linux-next.

Christian

             reply	other threads:[~2015-01-22 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 13:36 Christian Borntraeger [this message]
2015-01-22 21:39 ` kvms390 tree for Linux next Stephen Rothwell
2015-01-22 21:54   ` Christian Borntraeger
2015-01-22 22:59     ` Stephen Rothwell

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=54C0FCD0.7080108@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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.