public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ram Pai <linuxram@us.ibm.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Sam Ravnborg <sam@mars.ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: scripts/export_report.pl doesn't support O= builds
Date: Mon, 14 Aug 2006 22:42:20 -0700	[thread overview]
Message-ID: <1155620540.5724.362.camel@localhost> (raw)
In-Reply-To: <20060815021100.GI3543@stusta.de>

On Tue, 2006-08-15 at 04:11 +0200, Adrian Bunk wrote:
> scripts/export_report.pl doesn't support O= builds.
> 
> Could this be fixed?

Adrian,
	I am assuming you are expecting the functionality integrated in
	the kbuild?  

	If yes, I had the patch submitted long back. I
	can resubmit the patch. However Sam felt that having it
        integrated into the kbuild added little value.

RP



  reply	other threads:[~2006-08-15  5:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15  2:11 scripts/export_report.pl doesn't support O= builds Adrian Bunk
2006-08-15  5:42 ` Ram Pai [this message]
2006-08-27 21:46   ` Adrian Bunk

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=1155620540.5724.362.camel@localhost \
    --to=linuxram@us.ibm.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@mars.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