public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse•cz>
To: sfr@canb•auug.org.au
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	m.grzeschik@pengutronix•de
Subject: Re: [PATCH] kbuild: Fix reading of .config in link-vmlinux.sh
Date: Mon, 25 Feb 2013 13:56:42 +0100	[thread overview]
Message-ID: <512B5F8A.1060705@suse.cz> (raw)
In-Reply-To: <1361796898-19642-1-git-send-email-mmarek@suse.cz>

On 25.2.2013 13:54, Michal Marek wrote:
> The shell '.' command is not required to search the current directory as
> a fallback and in fact newer versions of bash in sh-mode do not do this.
> Force reading the file from the current directory if $KCONFIG_CONFIG
> contains no '/'.
> 
> Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
> Signed-off-by: Michal Marek <mmarek@suse•cz>
> ---
>  scripts/link-vmlinux.sh |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)

I was able to reproduce the failure and this patch fixed it. So I am
going to push this in a couple of hours, so that tomorrow's linux-next
can include the latest kbuild changes.

Michal

  reply	other threads:[~2013-02-25 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-24 23:56 linux-next: build failure after merge of the kbuild tree Stephen Rothwell
2013-02-25 10:28 ` Michal Marek
2013-02-25 10:58   ` Stephen Rothwell
2013-02-25 11:02     ` Stephen Rothwell
2013-02-25 11:36     ` Michal Marek
2013-02-25 12:54     ` [PATCH] kbuild: Fix reading of .config in link-vmlinux.sh Michal Marek
2013-02-25 12:56       ` Michal Marek [this message]
2013-02-25 14:11         ` Stephen Rothwell

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=512B5F8A.1060705@suse.cz \
    --to=mmarek@suse$(echo .)cz \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=m.grzeschik@pengutronix$(echo .)de \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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