From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox mailing list <barebox@lists.infradead.org>
Subject: Re: "make distclean" leaves a pile of arch/arm/dts/*.lzo files
Date: Fri, 11 Dec 2015 06:43:36 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1512110643001.4943@localhost> (raw)
In-Reply-To: <20151211070330.GP11966@pengutronix.de>
On Fri, 11 Dec 2015, Sascha Hauer wrote:
> Hi Robert,
>
> On Thu, Dec 10, 2015 at 10:28:18AM -0500, Robert P. J. Day wrote:
> >
> > just did a configure and build for a beaglebone black, then ran
> > "make distclean" and ...
> >
> > $ git status --ignored
> > On branch master
> > Your branch is up-to-date with 'origin/master'.
> > Ignored files:
> > (use "git add -f <file>..." to include in what will be committed)
> >
> > arch/arm/dts/am335x-afi-gf.dtb.lzo
> > arch/arm/dts/am335x-bone-common.dtb.lzo
> > arch/arm/dts/am335x-bone.dtb.lzo
> > arch/arm/dts/am335x-boneblack.dtb.lzo
> > arch/arm/dts/am335x-phytec-phycard-som-mlo.dtb.lzo
> > arch/arm/dts/am335x-phytec-phycard-som.dtb.lzo
> > arch/arm/dts/am335x-phytec-phycore-som-mlo.dtb.lzo
> > arch/arm/dts/am335x-phytec-phycore-som-no-eeprom.dtb.lzo
> > arch/arm/dts/am335x-phytec-phycore-som-no-spi-no-eeprom.dtb.lzo
> > arch/arm/dts/am335x-phytec-phycore-som-no-spi.dtb.lzo
> > arch/arm/dts/am335x-phytec-phycore-som.dtb.lzo
> > arch/arm/dts/am335x-phytec-phyflex-som-mlo.dtb.lzo
> > arch/arm/dts/am335x-phytec-phyflex-som-no-eeprom.dtb.lzo
> > arch/arm/dts/am335x-phytec-phyflex-som-no-spi-no-eeprom.dtb.lzo
> > arch/arm/dts/am335x-phytec-phyflex-som-no-spi.dtb.lzo
> > arch/arm/dts/am335x-phytec-phyflex-som.dtb.lzo
> > barebox-flash-images
> >
> > nothing to commit, working directory clean
> > $
> >
> > so i'm guessing building for other targets will also leave .lzo
> > files lying around.
>
> Added the following patch, this should fix this issue. Thanks for
> noting.
what about that last line, "barebox-flash-images"? should that also
be cleaned out?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-12-11 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 15:28 Robert P. J. Day
2015-12-11 7:03 ` Sascha Hauer
2015-12-11 11:43 ` Robert P. J. Day [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=alpine.LFD.2.20.1512110643001.4943@localhost \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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