mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: kernel test robot <lkp@intel.com>,
	"Minghao Chi (CGEL ZTE)" <chi.minghao@zte.com.cn>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [stable:linux-5.15.y 9126/9999] ERROR: modpost: "devm_drm_of_get_bridge" [drivers/gpu/drm/vc4/vc4.ko] undefined!
Date: Thu, 1 Sep 2022 11:03:38 +0200	[thread overview]
Message-ID: <YxB1akxCNlu5B2+M@kroah.com> (raw)
In-Reply-To: <20220901084833.fupxbfutuz6yqoqo@houat>

On Thu, Sep 01, 2022 at 10:48:33AM +0200, Maxime Ripard wrote:
> On Thu, Sep 01, 2022 at 10:39:36AM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Sep 01, 2022 at 10:00:17AM +0200, Maxime Ripard wrote:
> > > On Thu, Sep 01, 2022 at 12:51:57PM +0800, kernel test robot wrote:
> > > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.15.y
> > > > head:   1ded0ef2419e8f83a17d65594523ec3aeb2e3d0f
> > > > commit: 3d722c01d628d17a37cf2820195f15cfc9a6a332 [9126/9999] drm/vc4: Use of_device_get_match_data()
> > > > config: parisc-randconfig-c034-20220831 (https://download.01.org/0day-ci/archive/20220901/202209011256.zvBzxcpP-lkp@intel.com/config)
> > > > compiler: hppa-linux-gcc (GCC) 12.1.0
> > > > reproduce (this is a W=1 build):
> > > >         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > > >         chmod +x ~/bin/make.cross
> > > >         # https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=3d722c01d628d17a37cf2820195f15cfc9a6a332
> > > >         git remote add stable https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > > >         git fetch --no-tags stable linux-5.15.y
> > > >         git checkout 3d722c01d628d17a37cf2820195f15cfc9a6a332
> > > >         # save the config file
> > > >         mkdir build_dir && cp config build_dir/.config
> > > >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc SHELL=/bin/bash
> > > > 
> > > > If you fix the issue, kindly add following tag where applicable
> > > > Reported-by: kernel test robot <lkp@intel.com>
> > > > 
> > > > All errors (new ones prefixed by >>, old ones prefixed by <<):
> > > > 
> > > > >> ERROR: modpost: "devm_drm_of_get_bridge" [drivers/gpu/drm/vc4/vc4.ko] undefined!
> > > 
> > > I think this is due to stable having backported 87ea95808d53 and
> > > a43dd76bacd0, but missing 59050d7838482
> > 
> > I see no such commit as "59050d7838482" in Linus's tree, what are you
> > referring to exactly here?
> 
> Sorry, I meant 59050d783848, I'm not sure how the final 2 ended up there

Ah, that's better, now queued up, thanks!

greg k-h

      reply	other threads:[~2022-09-01  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  4:51 kernel test robot
2022-09-01  8:00 ` Maxime Ripard
2022-09-01  8:39   ` Greg Kroah-Hartman
2022-09-01  8:48     ` Maxime Ripard
2022-09-01  9:03       ` Greg Kroah-Hartman [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=YxB1akxCNlu5B2+M@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chi.minghao@zte.com.cn \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=maxime@cerno.tech \
    --cc=sashal@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®