public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: acme@ghostprotocols.net (Arnaldo Carvalho de Melo)
To: Andrew Morton <akpm@osdl.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: initramfs linus tree breakage in last day
Date: Sun, 3 Apr 2005 12:11:48 -0300	[thread overview]
Message-ID: <20050403151148.GB640@conectiva.com.br> (raw)
In-Reply-To: <20050401224431.6c06ca1e.akpm@osdl.org>

Em Fri, Apr 01, 2005 at 10:44:31PM -0800, Andrew Morton escreveu:
> Jon Smirl <jonsmirl@gmail.com> wrote:
> >
> > This will let me boot again. It is not obvious to me where the problem
> >  is, it may have something to do with netlink or maybe memory
> >  corruption?
> > 
> >  bk export -tpatch -r1.2326,1.2327 >../foo.patch
> >  patch -p1 -R <../foo.patch
> > 
> >  # ChangeSet
> >  #   2005/03/31 21:14:28-08:00 davem@sunset.davemloft.net
> >  #   Merge bk://kernel.bkbits.net/acme/net-2.6
> >  #   into sunset.davemloft.net:/home/davem/src/BK/net-2.6
> >  #
> >  # ChangeSet
> >  #   2005/03/26 20:04:49-03:00 acme@toy.ghostprotocols.net
> >  #   [NET] make all protos partially use sk_prot
> 
> Cute.  I assume you have all the memory debug options enabled?
> 
> You could try disabling net features in .config, see if you can work out
> which one causes it.

Question, what are the config choices for netlink?

- Arnaldo

  reply	other threads:[~2005-04-03 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02  2:18 initramfs linus tree breakage in last day Jon Smirl
2005-04-02  3:30 ` Jon Smirl
2005-04-02  6:22   ` Jon Smirl
2005-04-02  6:44     ` Andrew Morton
2005-04-03 15:11       ` Arnaldo Carvalho de Melo [this message]
2005-04-03 15:51   ` Arnaldo Carvalho de Melo
2005-04-03 16:36     ` Jon Smirl

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=20050403151148.GB640@conectiva.com.br \
    --to=acme@ghostprotocols.net \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=jonsmirl@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