public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Tony Finch <dot@dotat.at>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Joe Perches <joe@perches.com>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	"Justin P. Mattock" <justinmattock@gmail.com>
Subject: Re: [PATCH] unifdef: update to upstream revision 1.189
Date: Fri, 27 Nov 2009 22:04:08 +0100	[thread overview]
Message-ID: <20091127210408.GA16310@merkur.ravnborg.org> (raw)
In-Reply-To: <alpine.LSU.2.00.0911271901430.6581@hermes-1.csi.cam.ac.uk>

On Fri, Nov 27, 2009 at 07:15:01PM +0000, Tony Finch wrote:
> On Fri, 27 Nov 2009, Sam Ravnborg wrote:
> >
> > Can you confirm that this does not regress with respect to the changes
> > that Russell King implemented in the commit:
> > eedc9d83eaab2d35fb9dd1ec25b765dec964e26c
> > ("kbuild: fix headers_exports with boolean expression")
> 
> Yes. I ran the following commands:
> 
>   git checkout master
>   gmake distclean
>   gmake headers_install ARCH=i386 INSTALL_HDR_PATH=../include-master
>   git checkout fanf-unifdef
>   gmake distclean
>   gmake headers_install ARCH=i386 INSTALL_HDR_PATH=../include-fanf
>   diff -Nru -x ..install.cmd ../include-master ../include-fanf
> 
> and diff produced no output.

Good.

Michael - you can add my:

Acked-by: Sam Ravnborg <sam@ravnborg.org>

	Sam

  parent reply	other threads:[~2009-11-27 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 13:15 [PATCH] unifdef: update to upstream revision 1.189 Michal Marek
2009-11-27 21:04 ` Sam Ravnborg [this message]
     [not found]   ` <E1NE3M6-0003Za-OJ@hermes-1.csi.cam.ac.uk>
2009-11-27 18:17     ` Sam Ravnborg
2009-11-27 19:15       ` Tony Finch
2009-11-27 15:50         ` [PATCHv2] unifdef: update to upstream revision 1.190 Tony Finch
2009-12-01 16:12           ` Michal Marek
2009-12-01 16:21             ` Tony Finch

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=20091127210408.GA16310@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=dot@dotat.at \
    --cc=joe@perches.com \
    --cc=justinmattock@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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