From: Dominique Martinet <asmadeus@codewreck.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: Re: [martinetd:9p-next 11/13] ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined!
Date: Sun, 12 Jun 2022 21:23:37 +0900 [thread overview]
Message-ID: <YqXayRpfhqMwUjXe@codewreck.org> (raw)
In-Reply-To: <202206122057.RBESqurT-lkp@intel.com>
kernel test robot wrote on Sun, Jun 12, 2022 at 08:18:10PM +0800:
> >> ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined!
> >> ERROR: modpost: "p9_fid_get" [fs/9p/9p.ko] undefined!
Thanks, I had this fixed in my tree and in the patches I submitted to
the list but forgot to update the branch.
(looks like this was caught before the linux-next merge at least, that
was helpful)
--
Dominique
WARNING: multiple messages have this Message-ID (diff)
From: Dominique Martinet <asmadeus@codewreck.org>
To: kbuild-all@lists.01.org
Subject: Re: [martinetd:9p-next 11/13] ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined!
Date: Sun, 12 Jun 2022 21:23:37 +0900 [thread overview]
Message-ID: <YqXayRpfhqMwUjXe@codewreck.org> (raw)
In-Reply-To: <202206122057.RBESqurT-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
kernel test robot wrote on Sun, Jun 12, 2022 at 08:18:10PM +0800:
> >> ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined!
> >> ERROR: modpost: "p9_fid_get" [fs/9p/9p.ko] undefined!
Thanks, I had this fixed in my tree and in the patches I submitted to
the list but forgot to update the branch.
(looks like this was caught before the linux-next merge at least, that
was helpful)
--
Dominique
next prev parent reply other threads:[~2022-06-12 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 12:18 [martinetd:9p-next 11/13] ERROR: modpost: "p9_fid_put" [fs/9p/9p.ko] undefined! kernel test robot
2022-06-12 12:23 ` Dominique Martinet [this message]
2022-06-12 12:23 ` Dominique Martinet
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=YqXayRpfhqMwUjXe@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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.