linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Andreas Schwab <schwab@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: crash: IP: [<ffffffff80478092>] __bitmap_intersects+0x48/0x73 [PATCH supplied]
Date: Thu, 15 Jan 2009 12:34:55 -0800	[thread overview]
Message-ID: <496F9DEF.5060400@sgi.com> (raw)
In-Reply-To: <jepriolaat.fsf@sykes.suse.de>

Andreas Schwab wrote:
> Mike Travis <travis@sgi.com> writes:
> 
>>  23> git-remote update
>> Updating linus
>> Updating tip
> 
> This only updates the remotes, but does not merge anything into your
> local branch.  You need to run "git merge tip" to do that.
> 
> Andreas.
> 

Ahh, that's the secret ingredient!

In my particular instance it's:

	git merge tip/cpus4096

(Git has been quite a learning experience... ;-)

Thanks!
Mike
 

  reply	other threads:[~2009-01-15 21:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <496BF6D5.9030403@sgi.com>
     [not found] ` <20090113130048.GB31147@elte.hu>
     [not found]   ` <496CAF5A.3010304@sgi.com>
     [not found]     ` <496D0F46.2010907@sgi.com>
     [not found]       ` <496D2172.6030608@sgi.com>
     [not found]         ` <20090114165431.GA18826@elte.hu>
     [not found]           ` <20090114165524.GA21742@elte.hu>
     [not found]             ` <20090114175126.GA21078@elte.hu>
2009-01-14 23:43               ` crash: IP: [<ffffffff80478092>] __bitmap_intersects+0x48/0x73 [PATCH supplied] Mike Travis
2009-01-15 10:14                 ` Ingo Molnar
2009-01-15 16:44                   ` Mike Travis
2009-01-15 17:35                     ` Ingo Molnar
2009-01-15 17:59                     ` Andreas Schwab
2009-01-15 20:34                       ` Mike Travis [this message]
2009-01-16  9:44                         ` Andreas Schwab
2009-01-15 10:16                 ` Ingo Molnar
2009-01-15 12:21                   ` Ingo Molnar
2009-01-15 17:30                     ` Mike Travis
2009-01-15 17:37                       ` Ingo Molnar
2009-01-15 16:46                   ` Mike Travis

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=496F9DEF.5060400@sgi.com \
    --to=travis@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    /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).