From: Willy Tarreau <willy@w.ods.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH-2.4] make log buffer length selectable
Date: Wed, 27 Aug 2003 22:48:58 +0200 [thread overview]
Message-ID: <20030827204858.GA11660@alpha.home.local> (raw)
In-Reply-To: <20030827200922.GH32065@ip68-0-152-218.tc.ph.cox.net>
On Wed, Aug 27, 2003 at 01:09:22PM -0700, Tom Rini wrote:
> On Tue, Aug 26, 2003 at 06:25:50AM +0200, Willy Tarreau wrote:
> > On Mon, Aug 25, 2003 at 04:48:30AM -0700, Marcelo Tosatti wrote:
> > > final:
> > >
> > > - 2.4.22-rc4 was released as 2.4.22 with no changes.
> >
> > Hi Marcelo,
> >
> > as you requested, here is the log_buf_len patch for inclusion in 23-pre.
>
> Two things. First, why not ask on every arch like 2.6 does? Second:
I'm sorry, shame on me. It was an old one that I first showed as an example,
and I blindly resent without checking. I'll do my best to backport code in 2.6
on the next sleepless night.
> > +#if !defined(CONFIG_LOG_BUF_SHIFT) || (CONFIG_LOG_BUF_SHIFT - 0 == 0)
>
> Why not just || (CONFIG_LOG_BUF_SHIFT == 0) ?
It's an old trick I was used to, but at other places. Basically, it was used
to avoid syntax errors when the macro was not defined, which would lead to
(-0 == 0) which is valid while ( == 0) is not. But it appears that cpp handles
the case correctly so it's not needed here. I'll fix it too.
Marcelo, sorry for this quick patch, I'll better check what I feed you next
time.
Cheers,
Willy
prev parent reply other threads:[~2003-08-27 20:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 11:48 linux-2.4.22 released Marcelo Tosatti
2003-08-25 8:11 ` Enrico Demarin
2003-08-25 13:23 ` Matthias Andree
2003-08-25 13:32 ` Christoph Hellwig
2003-08-25 13:35 ` Ramón Rey Vicente
2003-08-25 21:13 ` J.A. Magallon
2003-08-25 22:22 ` Adrian Bunk
2003-08-26 0:21 ` Ramón Rey Vicente
2003-08-26 21:49 ` Diego Calleja García
2003-08-26 21:55 ` Adrian Bunk
2003-08-26 22:29 ` Diego Calleja García
2003-08-27 2:15 ` Ramón Rey Vicente
2003-08-27 5:21 ` Gerardo Exequiel Pozzi
2003-08-27 1:20 ` Chuck Campbell
2003-08-27 1:48 ` David van Hoose
2003-08-27 1:55 ` David van Hoose
2003-08-27 3:28 ` Kurt Wall
2003-08-27 2:01 ` Ramón Rey Vicente
2003-08-27 4:12 ` Willy Tarreau
2003-08-26 22:29 ` Matthias Andree
2003-08-27 9:47 ` Bas Mevissen
2003-08-26 13:55 ` Matthias Andree
2003-08-25 13:38 ` Nick Piggin
2003-08-25 22:34 ` Bill Davidsen
2003-08-25 14:38 ` Yann Droneaud
2003-08-25 15:35 ` Krzysztof Halasa
2003-08-25 16:03 ` Luca Montecchiani
2003-08-25 19:18 ` Erik Andersen
2003-08-25 20:00 ` Edesio Costa e Silva
2003-08-25 20:10 ` Tom Rini
2003-08-26 13:19 ` Rene Rebe
2003-08-26 15:00 ` Alan Cox
2003-08-27 3:47 ` CaT
2003-08-26 16:11 ` Willy Tarreau
2003-08-26 19:32 ` Greg KH
2003-08-26 1:52 ` cryptoapi doesn't build Tom Vier
2003-08-26 10:23 ` James Morris
2003-08-27 21:49 ` Tom Vier
2003-08-27 22:03 ` Marc-Christian Petersen
2003-08-26 4:25 ` [PATCH-2.4] make log buffer length selectable Willy Tarreau
2003-08-27 20:09 ` Tom Rini
2003-08-27 20:48 ` Willy Tarreau [this message]
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=20030827204858.GA11660@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=trini@kernel.crashing.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
Powered by JetHome