From: Martyn Welch <martyn.welch@collabora.com>
To: Jassi Brar <jassisinghbrar@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Andrew Davis <afd@ti.com>, Hari Nagalla <hnagalla@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
arnd@kernel.org
Subject: Re: linux-next: build warning after merge of the rpmsg tree
Date: Thu, 12 Sep 2024 16:32:34 +0100 [thread overview]
Message-ID: <a5f3b6c7029c9d431e28a8ba4ed886a1cf67fff9.camel@collabora.com> (raw)
In-Reply-To: <CABb+yY07P0zs6nT2CrZ+TnO+2XxZKYUfEjyRj2wwn+zAx9T0iQ@mail.gmail.com>
On Thu, 2024-09-12 at 09:15 -0500, Jassi Brar wrote:
> On Thu, Sep 12, 2024 at 3:34 AM Stephen Rothwell
> <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > On Fri, 06 Sep 2024 09:58:23 +0100 Martyn Welch
> > <martyn.welch@collabora.com> wrote:
> > >
> > > On Fri, 2024-09-06 at 18:36 +1000, Stephen Rothwell wrote:
> > > >
> > > > On Wed, 28 Aug 2024 15:09:00 +1000 Stephen Rothwell
> > > > <sfr@canb.auug.org.au> wrote:
> > > > >
> > > > > On Thu, 22 Aug 2024 14:26:03 +1000 Stephen Rothwell
> > > > > <sfr@canb.auug.org.au> wrote:
> > > > > >
> > > > > > After merging the rpmsg tree, today's linux-next build
> > > > > > (x86_64
> > > > > > allmodconfig) produced this warning:
> > > > > >
> > > > > > WARNING: unmet direct dependencies detected for
> > > > > > OMAP2PLUS_MBOX
> > > > > > Depends on [n]: MAILBOX [=y] && (ARCH_OMAP2PLUS ||
> > > > > > ARCH_K3)
> > > > > > Selected by [m]:
> > > > > > - TI_K3_M4_REMOTEPROC [=m] && REMOTEPROC [=y] && (ARCH_K3
> > > > > > || COMPILE_TEST [=y])
> > > > > >
> > > > > > Probably introduced by commit
> > > > > >
> > > > > > ebcf9008a895 ("remoteproc: k3-m4: Add a remoteproc driver
> > > > > > for M4F subsystem")
> > > > >
> > > > > I am still seeing this warning.
> > > >
> > > > I am still getting this warning.
> > >
> > > I believe this is the required fix, but I believe it's waiting
> > > for
> > > review/merging:
> > >
> > > https://lore.kernel.org/all/010201919d8b298f-dd1585dd-7c4d-4865-9483-ff6cd7399a90-000000@eu-west-1.amazonses.com/
> >
> > I am still getting this warning.
> >
> This
> https://lore.kernel.org/lkml/20240909203825.1666947-1-arnd@kernel.org/T/#u
> seems like a more complete solution.
>
> I am ok if it goes through TI or another tree.
>
> Acked-by: Jassi Brar <jassisinghbrar@gmail.com>
That solution works for me.
Martyn
next prev parent reply other threads:[~2024-09-12 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 4:26 Stephen Rothwell
2024-08-28 5:09 ` Stephen Rothwell
2024-08-28 9:45 ` Martyn Welch
2024-09-01 20:12 ` Jassi Brar
2024-09-06 8:36 ` Stephen Rothwell
2024-09-06 8:58 ` Martyn Welch
2024-09-12 8:34 ` Stephen Rothwell
2024-09-12 14:15 ` Jassi Brar
2024-09-12 15:32 ` Martyn Welch [this message]
2024-09-18 5:28 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2017-06-27 4:43 Stephen Rothwell
2017-06-27 23:47 ` Bjorn Andersson
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=a5f3b6c7029c9d431e28a8ba4ed886a1cf67fff9.camel@collabora.com \
--to=martyn.welch@collabora.com \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=arnd@kernel.org \
--cc=hnagalla@ti.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=sfr@canb.auug.org.au \
/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®