mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move some more intilization out of drivers/char/mem.c
Date: Sun, 21 Sep 2003 10:03:06 -0700	[thread overview]
Message-ID: <20030921100306.44949fb9.rddunlap@osdl.org> (raw)
In-Reply-To: <20030921070524.GA1992@lst.de>

On Sun, 21 Sep 2003 09:05:24 +0200 Christoph Hellwig <hch@lst.de> wrote:

| On Sat, Sep 20, 2003 at 11:48:53PM -0700, Andrew Morton wrote:
| > Christoph Hellwig <hch@lst.de> wrote:
| > >
| > > > Please compile-test things...
| > > 
| > >  Well, I compiled this here.  I see, looks like I lost half of the patch
| > >  when sending it to you.  Sorryh for that, here's the full patch:
| > 
| > It still generates warnings.  I suggest you build kernels with a script
| > which saves up stderr and spits it all out at the end.  That way, these
| > things are noticed.
| 
| Well, I do that, but they slipped through anyway.  I did a completle
| rebuild now and saw them.  I really need a filter for all those anoying
| warnings from the debian sid assembler..

I don't know what the assembler messages are, but I often do this:

make -j4 bzImage modules > buildk.out 2>&1

bldlogstrip buildk.out > buildkk.out

where 'bldlogstrip' is:

#! /bin/sh
# strip lines that contain CC, LD, "standard input", "In function"
egrep -v "CC|LD" $1 | grep -v "standard input" | grep -v "In function"

to get down to messages to focus on.

--
~Randy

  reply	other threads:[~2003-09-21 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-20 13:29 Christoph Hellwig
2003-09-20 23:06 ` Andrew Morton
2003-09-21  6:30   ` Christoph Hellwig
2003-09-21  6:48     ` Andrew Morton
2003-09-21  7:05       ` Christoph Hellwig
2003-09-21 17:03         ` Randy.Dunlap [this message]
2003-09-21  7:54       ` Muli Ben-Yehuda
2003-09-22 11:13         ` Adrian Bunk

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=20030921100306.44949fb9.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --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®