From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [Patch] kzalloc conversion in fs/proc
Date: Wed, 22 Feb 2006 19:29:44 +0000 [thread overview]
Message-ID: <20060222192944.GA30436@us.ibm.com> (raw)
In-Reply-To: <1140562907.26848.0.camel@alice>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On 22.02.2006 [22:14:25 +0300], Alexey Dobriyan wrote:
> On Wed, Feb 22, 2006 at 01:14:39AM +0100, Jesper Juhl wrote:
> > On 2/22/06, Eric Sesterhenn <snakebyte@gmx.de> wrote:
> > > On Wed, 2006-02-22 at 00:13 +0100, Jesper Juhl wrote:
> > > > This looks broken - did you even compile test that patch?
> > > >
> > > > Don't you mean :
> > > >
> > > > return kzalloc(sizeof(struct vmcore), GFP_KERNEL);
> > >
> > > *yuck*, sorry for this, didnt compile test since it doesnt build
> > > with my config. fixed patch below.
> > >
> >
> > Hmm, a simple
> >
> > $ make allyesconfig
> > $ make fs/proc/kcore.o
>
> How on earth did this succeed? I always, always get
I'm guessing it might have been a tree he's already built a kernel in
before? You usually need to let a normal make go through a few steps
before trying this, so that the asm->asm-$arch symlink is created and a
few other files are generated, IIRC.
Thanks,
Nish
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2006-02-22 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 23:01 [KJ] [Patch] kzalloc conversion in fs/proc Eric Sesterhenn
2006-02-21 23:13 ` Jesper Juhl
2006-02-22 0:01 ` Eric Sesterhenn
2006-02-22 0:14 ` Jesper Juhl
2006-02-22 0:14 ` Randy.Dunlap
2006-02-22 19:14 ` Alexey Dobriyan
2006-02-22 19:29 ` Eric Sesterhenn
2006-02-22 19:29 ` Nishanth Aravamudan [this message]
2006-02-22 19:51 ` Jaco Kroon
2006-02-22 20:24 ` Nishanth Aravamudan
2006-02-22 21:01 ` Alexey Dobriyan
2006-02-22 23:55 ` Jesper Juhl
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=20060222192944.GA30436@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=kernel-janitors@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 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.