mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
	"Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Willy Tarreau <willy@w.ods.org>
Subject: Re: [PATCH 2.4.23-pre1] /proc/ikconfig support
Date: Tue, 26 Aug 2003 22:23:08 +0200	[thread overview]
Message-ID: <200308262223.08827.m.c.p@wolk-project.de> (raw)
In-Reply-To: <Pine.LNX.4.55L.0308261629400.18109@freak.distro.conectiva>

On Tuesday 26 August 2003 21:33, Marcelo Tosatti wrote:

Hi Marcelo,

> > I have the same question about the seq_file "single" additions
> > patch that I sent yesterday.... ???
> The seq_file patch needs EXPORT_SYMBOL right?

I've send the export_symbol patch yesterday to you cc'ed lkml and randy etc.

> And about ikconfig, hum, I'm not sure if I want that. Its nice, yes, but I
> still wonder. You are free to convince me though: I think people usually
> know what they compile in their kernels, dont they?

grmpf. Absolutely wrong argumentation. People like me compile kernels a lot, 
for tons of different machines, for customers and so on. My brain is not that 
good that I'll remember each and every customers kernel/machine config ;)

Many people forget to copy the current .config to somewhere else in /boot or 
such. And I agree 100% with Willy :)

P.S.: Alan planed it for .23-pre1 ;-))

ciao, Marc


  parent reply	other threads:[~2003-08-26 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 19:33 Marcelo Tosatti
2003-08-26 20:09 ` Willy Tarreau
2003-08-26 20:23 ` Marc-Christian Petersen [this message]
2003-08-26 22:33 ` Matthias Andree
2003-08-26 23:06   ` Matt Gibson
2003-08-27 21:03 ` Herbert Pötzl

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=200308262223.08827.m.c.p@wolk-project.de \
    --to=m.c.p@wolk-project.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rddunlap@osdl.org \
    --cc=willy@w.ods.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®