All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the rpmsg tree
Date: Thu, 31 Aug 2017 10:47:37 -0700	[thread overview]
Message-ID: <20170831174737.GS29306@minitux> (raw)
In-Reply-To: <20170831165447.064fab6f@canb.auug.org.au>

On Wed 30 Aug 23:54 PDT 2017, Stephen Rothwell wrote:

> Hi Bjorn,
> 
> After merging the rpmsg tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> ERROR: "qcom_glink_native_probe" [drivers/rpmsg/qcom_glink_rpm.ko] undefined!
> ERROR: "qcom_glink_native_remove" [drivers/rpmsg/qcom_glink_rpm.ko] undefined!
> 
> Maybe caused by commit
> 
>   6799c434c27b ("rpmsg: glink: Split rpm_probe to reuse the common code")
> 

Thanks for letting me know Stephen, those functions should have been
exported and I've corrected it.

> I have used the rpmsg tree from next-20170829 for today.
> 

Thanks,
Bjorn

  reply	other threads:[~2017-08-31 17:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31  6:54 linux-next: build failure after merge of the rpmsg tree Stephen Rothwell
2017-08-31 17:47 ` Bjorn Andersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-26  3:33 Stephen Rothwell
2018-04-26  3:46 ` Bjorn Andersson
2019-02-22  5:18 Stephen Rothwell
2019-02-22 12:50 ` Christoph Hellwig
2019-02-22 14:02   ` Loic PALLARDY
2020-10-15  4:55 Stephen Rothwell
2023-01-27  7:02 Stephen Rothwell
2023-01-30  8:51 ` Joerg Roedel
2024-06-26 18:44 Mark Brown
2024-07-01  7:26 ` Stephen Rothwell
2024-07-01 10:08   ` Dmitry Baryshkov

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=20170831174737.GS29306@minitux \
    --to=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.