mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@suse.de>
Cc: H Hartley Sweeten <hartleys@visionengravers.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"ss@aao.gov.au" <ss@aao.gov.au>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Staging: dt3155: Cleanup memory mapped i/o access
Date: Tue, 04 May 2010 12:07:11 -0700	[thread overview]
Message-ID: <1273000031.4143.56.camel@Joe-Laptop.home> (raw)
In-Reply-To: <20100504025430.GA26421@suse.de>

On Mon, 2010-05-03 at 19:54 -0700, Greg KH wrote: 
> > git push?
> I have, and they look to be there to me:
>   http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-next-2.6.git;a=commit;h=4f923d004396ef272600d381a365cac9d832486d
> So something must be odd on your side.

Yup, sorry, my mistake.

staging-next is the name of your repository as well as
a branch within your repository and git after git clone
doesn't by default show all remote branches.

$ git clone --reference=linux-2.6 \
	git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-next-2.6.git

$ git branch -r
  origin/HEAD -> origin/master
  origin/master
  origin/staging-next

I needed to add a git checkout origin/staging-next



  reply	other threads:[~2010-05-04 19:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 17:23 [PATCH] " H Hartley Sweeten
2010-04-30 21:56 ` Greg KH
2010-05-02 17:35   ` H Hartley Sweeten
2010-05-02 18:00   ` H Hartley Sweeten
2010-05-03 18:59     ` Greg KH
2010-05-03 20:15       ` H Hartley Sweeten
2010-05-03 21:17         ` Greg KH
2010-05-03 22:24           ` H Hartley Sweeten
2010-05-03 22:45           ` H Hartley Sweeten
2010-05-03 23:33             ` H Hartley Sweeten
2010-05-03 23:40               ` Greg KH
2010-05-03 23:41               ` Greg KH
2010-05-03 23:59                 ` Joe Perches
2010-05-04  2:54                   ` Greg KH
2010-05-04 19:07                     ` Joe Perches [this message]
2010-05-04 20:02                       ` H Hartley Sweeten
2010-05-04 20:12                         ` Greg KH
2010-05-04 20:53                           ` H Hartley Sweeten
2010-05-04 21:02                             ` Greg KH
2010-05-04 21:22                               ` H Hartley Sweeten
2010-05-06 16:59                                 ` H Hartley Sweeten
2010-05-06 20:25                                   ` Greg KH
2010-06-21 15:51                                     ` [PATCH v2] " H Hartley Sweeten
2010-06-22 22:39                                       ` Greg KH
2010-06-22 22:45                                         ` H Hartley Sweeten
2010-06-22 23:04                                           ` Greg KH
2010-06-22 23:36                                             ` H Hartley Sweeten
2010-05-04  0:49                 ` H Hartley Sweeten
2010-06-22 23:38 [PATCH v2] " H Hartley Sweeten
2010-06-23 22:23 ` 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=1273000031.4143.56.camel@Joe-Laptop.home \
    --to=joe@perches.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=hartleys@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ss@aao.gov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®