All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git pull] PCI changes
Date: Fri, 21 May 2010 20:01:39 -0700	[thread overview]
Message-ID: <20100521200139.30e60c62@virtuousgeek.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1005211859030.3689@i5.linux-foundation.org>

On Fri, 21 May 2010 18:59:58 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> 
> On Fri, 21 May 2010, Linus Torvalds wrote:
> >
> > I think the "not verified" is also because you actually didn't push it 
> > out..
> > 
> > I'm getting "Already up-to-date".
> > 
> > Or is it in some magic branch that you didn't actually mention at all?
> 
> Ahh. It's in "linux-next". Not "for-linus" or "master".

Yeah sorry, I had pushed but it hadn't mirrored yet...

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-05-22  3:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 21:48 [git pull] PCI changes Jesse Barnes
2010-05-22  0:12 ` Linus Torvalds
2010-05-22  1:59   ` Linus Torvalds
2010-05-22  3:01     ` Jesse Barnes [this message]
2010-05-22  8:17       ` Pekka Enberg
  -- strict thread matches above, loose matches on Subject: below --
2010-08-05 19:52 Jesse Barnes
2011-01-14 17:01 Jesse Barnes
2011-03-18 17:30 Jesse Barnes
2011-05-23 20:43 Jesse Barnes
2011-05-23 21:16 ` David Miller
2011-05-24  0:04   ` Jesse Barnes
2011-07-28 23:51 Jesse Barnes
2011-10-28 20:29 Jesse Barnes
2011-10-28 23:30 ` Rafael J. Wysocki
2011-10-31 17:18   ` Jesse Barnes
2012-01-11 18:34 Jesse Barnes
2012-01-12  3:38 ` Linus Torvalds
2012-01-13 21:24   ` Matthew Garrett
2012-01-13 23:14     ` Linus Torvalds
2012-01-13 23:26       ` Matthew Garrett
2012-01-12  5:34 ` Yinghai Lu

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=20100521200139.30e60c62@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=torvalds@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 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.