From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
linux-pci@vger.kernel.org, Jean-Jacques Hiblot <jjhiblot@ti.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH v1] tools: PCI: Fix installation when `make tools/pci_install`
Date: Fri, 5 Jul 2019 20:08:53 +0300 [thread overview]
Message-ID: <20190705170853.GG9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190705162358.GA3080@e121166-lin.cambridge.arm.com>
On Fri, Jul 05, 2019 at 05:23:58PM +0100, Lorenzo Pieralisi wrote:
> On Fri, Jun 28, 2019 at 04:33:26PM +0300, Andy Shevchenko wrote:
> > The commit c9a707875053 ("tools pci: Do not delete pcitest.sh in 'make clean'")
> > fixed a `make tools clean` issue and simultaneously brought a regression
> > to the installation process:
> >
> > for script in .../tools/pci/pcitest.sh; do \
> > install $script .../usr/usr/bin; \
> > done
> > install: cannot stat '.../tools/pci/pcitest.sh': No such file or directory
> >
> > Here is the missed part of the fix.
>
> Sigh, hopefully that's the last fix :), Kishon if that's OK mind
> ACKing it please ?
From my side, yes. Now it works as I expect.
Honestly, I'm puzzled how so many errors has been pushed upstream...
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-07-05 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 13:33 [PATCH v1] tools: PCI: Fix installation when `make tools/pci_install` Andy Shevchenko
2019-07-05 16:23 ` Lorenzo Pieralisi
2019-07-05 17:08 ` Andy Shevchenko [this message]
2019-07-09 11:18 ` Kishon Vijay Abraham I
2019-07-09 11:38 ` Andy Shevchenko
2019-07-09 11:43 ` Kishon Vijay Abraham I
2019-07-09 11:45 ` Kishon Vijay Abraham I
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=20190705170853.GG9224@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=acme@redhat.com \
--cc=jjhiblot@ti.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
/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