From: Michal Marek <mmarek@suse.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kbuild@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checksyscalls: Fix stand-alone usage
Date: Mon, 20 Dec 2010 15:43:30 +0100 [thread overview]
Message-ID: <20101220144329.GA20492@sepie.suse.cz> (raw)
In-Reply-To: <20100825133027.GA1745@merkur.ravnborg.org>
On Wed, Aug 25, 2010 at 03:30:27PM +0200, Sam Ravnborg wrote:
> On Wed, Aug 25, 2010 at 12:22:40PM +0200, Geert Uytterhoeven wrote:
> > The usage help in the comments
> > - refers to the wrong script name,
> > - doesn't mention that $srctree must be set.
> >
> > Hence correct the script name, and derive the source tree path from the script
> > path, so we no longer need to rely on $srctree being set by the caller.
> >
> > Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
Applied to kbuild-2.6.git#kbuild, thanks.
Michal
prev parent reply other threads:[~2010-12-20 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 10:22 [PATCH] checksyscalls: Fix stand-alone usage Geert Uytterhoeven
2010-08-25 13:30 ` Sam Ravnborg
2010-12-20 14:43 ` Michal Marek [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=20101220144329.GA20492@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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