From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Vinod Koul <vkoul@kernel.org>
Cc: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL]: dmaengine updates for v5.7-rc1
Date: Fri, 3 Apr 2020 17:09:57 +0300 [thread overview]
Message-ID: <b4edfea1-ef1b-70bf-cae9-da1276ab8bef@ti.com> (raw)
In-Reply-To: <CAHk-=wi81+9roQMgf7n0YRxJ0rqK3W0ghB3tS3kngSikC7cOig@mail.gmail.com>
Hi Linus,
On 03/04/2020 2.28, Linus Torvalds wrote:
> On Thu, Apr 2, 2020 at 4:25 AM Vinod Koul <vkoul@kernel.org> wrote:
>>
>> Here are the changes for this cycle. SFR has told me that you might see
>> a merge conflict, but I am sure you would be okay with it :)
>
> It looked trivial enough. That said, it's in the TI_K3_UDMA driver,
> which I can't build. The driver is marked as COMPILE_TEST, but it also
> has
>
> depends on TI_SCI_PROTOCOL
> depends on TI_SCI_INTA_IRQCHIP
Right.
> which means that it depends on TI_MESSAGE_MANAGER, which in turn has a
>
> depends on ARCH_KEYSTONE || ARCH_K3
And the INTA_IRQCHIP needs INTA_MSI_DOMAIN.
and the UDMA driver actually needs the ringacc.
It goes pretty deep it looks like.
> so it may be *marked* for build testing, but it doesn't actually get
> any outside of those builds.
Yep, sadly this is true.
> So I did the resolution that looked trivial, but mistakes happen, and
> I can't even build-test that driver..
>
> Just a heads-up. It does look like it was _meant_ to be build-tested,
> but that intent didn't work out.
The merge was correct, thank you!
> Adding a COMPILE_TEST option to TI_MESSAGE_MANAGER gets things a bit
> further, but even then it doesn't actually build that driver because
> that TI_SCI_INTA_IRQCHIP dependency needs to be enabled too.
>
> And that one doesn't even have a question, it's just a plain bool, and
> expects to be selected. Which the arm64 platform does.
Yes, I'll sort this out. I prefer my drivers to be compile tested.
> Anyway, to make a long story short: "the COMPILE_TEST marker is a lie".
I'll remove the lie for now and fix things up so I will have legal
grounds to put it back.
> So somebody should actually test my merge.
Tested, thank you again!
>
> Linus
>
- Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-04-03 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 11:25 Vinod Koul
2020-04-02 23:28 ` Linus Torvalds
2020-04-03 7:39 ` Vinod Koul
2020-04-03 14:09 ` Peter Ujfalusi [this message]
2020-04-03 0:40 ` pr-tracker-bot
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=b4edfea1-ef1b-70bf-cae9-da1276ab8bef@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®