From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.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: Tue, 9 Jul 2019 14:38:22 +0300 [thread overview]
Message-ID: <20190709113822.GV9224@smile.fi.intel.com> (raw)
In-Reply-To: <7c48dbae-847b-812d-88f3-7336686bd46e@ti.com>
On Tue, Jul 09, 2019 at 04:48:57PM +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On 05/07/19 10:38 PM, Andy Shevchenko wrote:
> > 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...
>
> I'm not sure why, but I don't see any issue without this patch as well. Am I
> missing something here?
Yes.
I'm not contaminate my Linux kernel tree with any build stuff, so, I'm using
the folder which is out to the build, i.e.
% make O=/xyz ...
> I'm copy pasting the steps below.
>
> a0393678@a0393678ub:~/repos/linux/tools/pci$ make clean
> rm -f pcitest
> rm -rf include/
> find . -name '*.o' -delete -o -name '\.*.d' -delete
> a0393678@a0393678ub:~/repos/linux/tools/pci$ make
> mkdir -p include/linux/ 2>&1 || true
> ln -sf /home/a0393678/repos/linux/tools/pci/../../include/uapi/linux/pcitest.h
> include/linux/
> make -f /home/a0393678/repos/linux/tools/build/Makefile.build dir=. obj=pcitest
> make[1]: Entering directory '/home/a0393678/repos/linux/tools/pci'
> CC pcitest.o
> LD pcitest-in.o
> make[1]: Leaving directory '/home/a0393678/repos/linux/tools/pci'
> LINK pcitest
> a0393678@a0393678ub:~/repos/linux/tools/pci$ sudo make install
> make -f /home/a0393678/repos/linux/tools/build/Makefile.build dir=. obj=pcitest
> install -d -m 755 /usr/bin; \
> for program in pcitest pcitest.sh; do \
> install $program /usr/bin; \
> done; \
> for script in pcitest.sh; do \
> install $script /usr/bin; \
> done
> a0393678@a0393678ub:~/repos/linux/tools/pci$
>
> Thanks
> Kishon
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-07-09 11:38 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
2019-07-09 11:18 ` Kishon Vijay Abraham I
2019-07-09 11:38 ` Andy Shevchenko [this message]
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=20190709113822.GV9224@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