mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Adrian Bunk <bunk@kernel.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Nick Andrew <nick@nick-andrew.net>,
	Matthew Wilcox <matthew@wil.cx>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] headerdep: a tool for detecting inclusion cycles in header files
Date: Thu, 18 Dec 2008 20:24:33 +0100	[thread overview]
Message-ID: <20081218192433.GA15206@uranus.ravnborg.org> (raw)
In-Reply-To: <20081216115249.GA3901@localhost.localdomain>

> 
> This one is probably a bit too noisy? But if we can eliminate the existing
> cycles, it would be nice, I agree. Thanks for the feedback! :)

Applied to kbuild-next.

	Sam

      reply	other threads:[~2008-12-18 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 20:27 Vegard Nossum
2008-12-13 22:22 ` Sam Ravnborg
2008-12-16 11:52   ` Vegard Nossum
2008-12-18 19:24     ` Sam Ravnborg [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=20081218192433.GA15206@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bunk@kernel.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=nick@nick-andrew.net \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@gmail.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

Powered by JetHome