mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Lane <miles.lane@gmail.com>
To: Jie Yang <Jie.Yang@atheros.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Jay Cliburn <jcliburn@gmail.com>,
	Chris Snook <chris.snook@gmail.com>
Subject: Re: 2.6.32-rc6-git4 -- NetworkManager: page allocation failure.  order:8, mode:0x8020
Date: Sun, 15 Nov 2009 23:18:06 -0500	[thread overview]
Message-ID: <a44ae5cd0911152018qf913307n5506fc2772fc5e60@mail.gmail.com> (raw)
In-Reply-To: <72981EBCFD196144B7C6999B9FC34A9A494C18F02B@SHEXMB-01.global.atheros.com>

I download the latest linux tarball in bz2 format from ftp.kernel.org
and then apply the patches there.  For example:

    tar xvfj linux-2.6.31.tar.bz2
    cd linux
    bzcat ../patch-2.4.32-rc6.bz2 | patch -p1
    bzcat ../patch-2.4.32-rc6-git4.bz2 | patch -p1
    make defconfig

    and so forth


On Sun, Nov 15, 2009 at 9:21 PM, Jie Yang <Jie.Yang@atheros.com> wrote:
> On Thursday, November 12, 2009 3:58 AM
> Miles Lane <miles.lane@gmail.com> wrote:
>> Subject: Re: 2.6.32-rc6-git4 -- NetworkManager: page
>> allocation failure. order:8, mode:0x8020
>>
>> This is completely reproducible with this kernel.  I get the
>> error on boot, and then I get it again each time I wake the
>> OS from the suspend state.
>>
>>         Miles
>>
>
> hi,     Miles
> it seems that after git-pull my git-tag -l
> result is
> ... ...
> v2.6.31-rc9
> v2.6.32-rc1
> v2.6.32-rc3
>
> how can i get the 2.6.32-rc6-git4 version.
>
> best wishes
> jie
>
>
>

  reply	other threads:[~2009-11-16  4:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 19:41 Miles Lane
2009-11-11 19:58 ` Miles Lane
2009-11-12  1:35   ` Jie Yang
2009-11-16  2:21   ` Jie Yang
2009-11-16  4:18     ` Miles Lane [this message]
2009-11-16  4:27       ` Jie Yang
2009-11-16  4:58         ` Miles Lane

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=a44ae5cd0911152018qf913307n5506fc2772fc5e60@mail.gmail.com \
    --to=miles.lane@gmail.com \
    --cc=Jie.Yang@atheros.com \
    --cc=chris.snook@gmail.com \
    --cc=jcliburn@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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®