From: Dan Murphy <dmurphy@ti.com>
To: <davem@davemloft.net>, <richardcochran@gmail.com>,
<ivan.khoronzhuk@linaro.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH net/master] net: ethernet: ti: cpts: Fix linker issue when TI_CPTS is defined
Date: Thu, 7 May 2020 19:31:33 -0500 [thread overview]
Message-ID: <ab0a9a19-c96b-f90f-827d-aa10bf49a4b7@ti.com> (raw)
In-Reply-To: <20200507214740.14693-1-dmurphy@ti.com>
All
On 5/7/20 4:47 PM, Dan Murphy wrote:
> Fix build issue when CONFIG_TI_CPTS is defined in the defconfig but
> CONFIG_TI_CPTS_MOD is not set.
I see this already has a pending patch to fix this so unless this
solution is better I will drop the patch
https://lore.kernel.org/patchwork/patch/1235642/
Dan
prev parent reply other threads:[~2020-05-08 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 21:47 [PATCH net/master] net: ethernet: ti: cpts: Fix linker issue when TI_CPTS is defined Dan Murphy
2020-05-08 0:31 ` Dan Murphy [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=ab0a9a19-c96b-f90f-827d-aa10bf49a4b7@ti.com \
--to=dmurphy@ti.com \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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;
as well as URLs for NNTP newsgroup(s).