public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: John Levon <movement@marcelothewonderpenguin.com>
Cc: Thunder from the hill <thunder@ngforever.de>,
	Adrian Bunk <bunk@fs.tum.de>,
	Guillaume Boissiere <boissiere@adiglobal.com>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>, bob <bob@watson.ibm.com>,
	Richard Moore <richardj_moore@uk.ibm.com>
Subject: Re: [STATUS 2.5]  July 10, 2002
Date: Wed, 10 Jul 2002 15:19:46 -0400	[thread overview]
Message-ID: <3D2C88D2.B5FF2DC2@opersys.com> (raw)
In-Reply-To: 20020710172513.GB49811@compsoc.man.ac.uk


John Levon wrote:
> On Wed, Jul 10, 2002 at 12:54:49PM -0400, Karim Yaghmour wrote:
> 
> > In light of the recent discussions, it would be really nice to get a
> > definitive statement about LTT's inclusion in 2.5.
> 
> It has been pointed out to you at least once that it would stand a much
> better chance if you were to follow the kernel coding style, for one ...

And if you had actually cared to follow that thread with Roman Zippel to
its logical conclusion, you would have noticed that patches including an
update to match the coding style have been made available:
http://marc.theaimsgroup.com/?l=linux-kernel&m=102106555627527&w=2

> And things like :
> 
> +#ifndef CONFIG_SMP /* On an SMP machine NMIs are used to implement a watchdog and will hang
> +                      the machine if traced. */
> +        TRACE_TRAP_ENTRY(2, regs->eip);
> +#endif
> +
> 
> aren't very encouraging.

Care to comment on why? All what the above says is that this trace point
shouldn't be active on an SMP box. That's one of the very rare cases
(if not the only case) where such a build-condition is added. And if this
really is too much for the kernel crowd's stomach then it is easily remedied.

I would have thought you had something a little bit more substantial
to stand against LTT's inclusion.

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

  reply	other threads:[~2002-07-10 19:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10  5:11 [STATUS 2.5] July 10, 2002 Guillaume Boissiere
2002-07-10 15:49 ` Rik van Riel
2002-07-10 16:19 ` Adrian Bunk
2002-07-10 16:31   ` Thunder from the hill
2002-07-10 16:51     ` Roman Zippel
2002-07-10 17:00       ` Thunder from the hill
2002-07-10 16:54     ` Karim Yaghmour
2002-07-10 17:25       ` John Levon
2002-07-10 19:19         ` Karim Yaghmour [this message]
2002-07-10 17:17     ` Alan Cox
2002-07-10 20:21     ` Daniel Phillips
2002-07-10 17:12 ` Patrick Mochel
2002-07-10 17:42 ` Arnaldo Carvalho de Melo
2002-07-10 17:54 ` Robert Love
2002-07-10 19:18   ` Ville Herva
2002-07-10 20:03     ` Robert Love
2002-07-10 20:20       ` Cort Dougan
2002-07-10 20:25         ` Robert Love
2002-07-10 20:41           ` Ville Herva
2002-07-10 21:07         ` Alan Cox
2002-07-10 20:46           ` Robert Love
2002-07-11  9:46           ` Rogier Wolff
2002-07-10 20:26     ` Justin M. Forbes
  -- strict thread matches above, loose matches on Subject: below --
2002-07-10 17:46 Perches, Joe
2002-07-10 18:05 ` Thunder from the hill
2002-07-10 18:38 ` Alan Cox
2002-07-10 18:49   ` Kurt Garloff
2002-07-10 19:19     ` Larry Kessler
2002-07-10 21:15       ` Alan Cox
2002-07-11 18:07         ` Anton Blanchard
2002-07-10 21:27     ` Alan Cox
2002-07-10 18:08 Russ Weight
2002-07-11 19:21 Richard J Moore
2002-07-11 20:34 Richard J Moore
2002-07-13  9:28 ` Ingo Oeser

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=3D2C88D2.B5FF2DC2@opersys.com \
    --to=karim@opersys.com \
    --cc=bob@watson.ibm.com \
    --cc=boissiere@adiglobal.com \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=movement@marcelothewonderpenguin.com \
    --cc=richardj_moore@uk.ibm.com \
    --cc=thunder@ngforever.de \
    --cc=torvalds@transmeta.com \
    /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