All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: anthony.perard@citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] tools: provide distclean target for OVMF
Date: Mon, 2 Mar 2015 14:35:31 +0000	[thread overview]
Message-ID: <1425306931.21151.62.camel@citrix.com> (raw)
In-Reply-To: <20150302143130.GE11855@zion.uk.xensource.com>

On Mon, 2015-03-02 at 14:31 +0000, Wei Liu wrote:
> On Mon, Mar 02, 2015 at 02:20:57PM +0000, Ian Campbell wrote:
> > On Mon, 2015-03-02 at 10:52 +0000, Wei Liu wrote:
> > > OVMF's distclean target was missed in f9c9b1277 (tools: fix "make
> > > distclean").
> > 
> > tools/firmware/Makefile has:
> > subdir-distclean-ovmf: .phony
> >         rm -rf ovmf-dir ovmf-dir-remote
> > 
> > Shouldn't this be avoiding recursing into ovmf-dir in the first place?
> > 
> > Or is there some other reason to want this?
> > 
> 
> If you're in firmware directory and do "make distclean", make will
> recurse into ovmf to do "make distclean".

Really? Despite the rule I quoted above? How strange, I wonder why that
is.

I'd have expected "make distclean" to behave the same whether run in the
directory or recursed into frmo a higher level.

> 
> Wei.
> 
> > > 
> > > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> > > Cc: Anthony Perard <anthony.perard@citrix.com>
> > > Cc: Ian Campbell <ian.campbell@citrix.com>
> > > Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> > > ---
> > >  tools/firmware/ovmf-makefile | 3 +++
> > >  1 file changed, 3 insertions(+)
> > > 
> > > diff --git a/tools/firmware/ovmf-makefile b/tools/firmware/ovmf-makefile
> > > index 2838744..c922d4d 100644
> > > --- a/tools/firmware/ovmf-makefile
> > > +++ b/tools/firmware/ovmf-makefile
> > > @@ -22,3 +22,6 @@ build:
> > >  .PHONY: clean
> > >  clean:
> > >  	rm -rf ovmf.bin Build/*
> > > +
> > > +.PHONY: distclean
> > > +distclean: clean
> > 

  reply	other threads:[~2015-03-02 14:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 10:52 [PATCH 0/2] Two patches for OVMF build system Wei Liu
2015-03-02 10:52 ` [PATCH 1/2] tools: OVMF parallel build Wei Liu
2015-03-02 14:18   ` Ian Campbell
2015-03-02 15:17     ` Wei Liu
2015-03-11 16:41     ` Ian Campbell
2015-03-11 16:47       ` Wei Liu
2015-03-02 10:52 ` [PATCH 2/2] tools: provide distclean target for OVMF Wei Liu
2015-03-02 14:20   ` Ian Campbell
2015-03-02 14:31     ` Wei Liu
2015-03-02 14:35       ` Ian Campbell [this message]
2015-03-02 14:45         ` Wei Liu
2015-03-02 14:54           ` Ian Campbell

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=1425306931.21151.62.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.