All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: set_phys_to_machine not exported?
Date: Tue, 3 Jan 2012 18:48:33 -0500	[thread overview]
Message-ID: <20120103234833.GB19899@phenom.dumpdata.com> (raw)
In-Reply-To: <6035A0D088A63A46850C3988ED045A4B093177@BITCOM1.int.sbss.com.au>

On Tue, Jan 03, 2012 at 11:44:53PM +0000, James Harper wrote:
> > > Or maybe someone else already has scsiback working against 3.x.x?
> > 
> > I do. Try the #testing branch or the #devel/xen-scsi-1.0 (but you should
> > merge it against the 3.1 kernel otherwise it won't compile b/c one argument
> > changed - but you could alter it yourself if you are using the 3.0 tree).
> > 
> > Git tree: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> > 
> > They also moved - to drivers/scsi.
> 
> My git-foo is a bit rusty. Having cloned the tree, how do I check out the remote branch?

git checkout origin/testing

> 
> James

  reply	other threads:[~2012-01-03 23:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30 12:06 set_phys_to_machine not exported? James Harper
2012-01-03 17:55 ` Konrad Rzeszutek Wilk
2012-01-03 20:10   ` James Harper
2012-01-03 22:36     ` Konrad Rzeszutek Wilk
2012-01-03 23:44       ` James Harper
2012-01-03 23:48         ` Konrad Rzeszutek Wilk [this message]
2012-01-04  0:20       ` James Harper
2012-01-04  1:50       ` James Harper
2012-01-04  3:44         ` James Harper
2012-01-04 10:21           ` Jan Beulich
2012-01-04 10:34             ` James Harper
2012-01-04 14:48           ` Konrad Rzeszutek Wilk
2012-01-04 14:47         ` Konrad Rzeszutek Wilk

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=20120103234833.GB19899@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=konrad@darnok.org \
    --cc=xen-devel@lists.xensource.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 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.