All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] potential parse error in ifdef
Date: Mon, 21 May 2007 17:01:39 +0000	[thread overview]
Message-ID: <20070521170138.GA18519@parisc-linux.org> (raw)
In-Reply-To: <87fy5q5dxr.fsf@wanadoo.fr>

On Mon, May 21, 2007 at 06:39:12PM +0200, Yoann Padioleau wrote:
> I have made a tool to parse the kernel that does not pre-process the
> source. That means that my parser tries to parse all the code, including
> code in the #else branch or code that is not often compiled because
> the driver is not very used (or not used at all). So, my parser
> sometimes reports parse error not originally detected by gcc. 
> Here is my (first) patch.

These all look good to me.

Acked-by: Matthew Wilcox <matthew@wil.cx>
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2007-05-21 17:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 16:39 [KJ] [PATCH] potential parse error in ifdef Yoann Padioleau
2007-05-21 17:01 ` Matthew Wilcox [this message]
2007-05-22  8:21 ` Yoann Padioleau
2007-05-22 23:10 ` Håkon Løvdal
2007-05-22 23:12 ` Cripps
2007-05-23  7:32 ` walter harms
2007-05-23  7:46 ` Yoann Padioleau
2007-05-23  8:18 ` Robert P. J. Day
2007-05-25  7:56 ` Yoann Padioleau
2007-05-25  7:56   ` Yoann Padioleau
2007-05-25 11:50   ` [KJ] " Jiri Kosina
2007-05-25 11:50     ` Jiri Kosina
2007-05-25 16:41     ` [KJ] " Andrew Morton
2007-05-25 16:41       ` Andrew Morton
2007-06-04 18:29 ` [KJ] [PATCH] potential parse error in ifdef part 3 Yoann Padioleau
2007-06-04 18:29   ` Yoann Padioleau
2007-06-05  7:43   ` [KJ] " Geert Uytterhoeven
2007-06-05  7:43     ` Geert Uytterhoeven

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=20070521170138.GA18519@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.