From: David Miller <davem@davemloft.net>
To: irusskikh@marvell.com
Cc: netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH net] net: atlantic: fix build when object tree is separate
Date: Fri, 25 Sep 2020 17:19:36 -0700 (PDT) [thread overview]
Message-ID: <20200925.171936.1056795284957056658.davem@davemloft.net> (raw)
In-Reply-To: <20200925202735.3296-1-irusskikh@marvell.com>
From: Igor Russkikh <irusskikh@marvell.com>
Date: Fri, 25 Sep 2020 23:27:35 +0300
> Driver subfolder files refer parent folder includes in an
> absolute manner.
>
> Makefile contains a -I for this, but apparently that does not
> work if object tree is separated.
>
> Adding srctree to fix that.
>
> Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
Applied.
prev parent reply other threads:[~2020-09-26 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 20:27 [PATCH net] net: atlantic: fix build when object tree is separate Igor Russkikh
2020-09-26 0:19 ` David Miller [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=20200925.171936.1056795284957056658.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).