From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Markus Probst <markus.probst@posteo.de>,
oe-kbuild-all@lists.linux.dev, linux-serial@vger.kernel.org
Subject: Re: [tty:tty-testing 11/13] error[E0425]: cannot find type `BoundInternal` in module `device`
Date: Fri, 17 Jul 2026 15:16:04 +0200 [thread overview]
Message-ID: <2026071755-overture-crunchy-bfaa@gregkh> (raw)
In-Reply-To: <202607171517.ScFnGK4R-lkp@intel.com>
On Fri, Jul 17, 2026 at 03:07:34PM +0200, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
> head: ec7dbdaa11c7be1806f0ea1a272ee6daee42a843
> commit: cbc11f4e978d1ee0bc857a9c51d43bbae6966f1d [11/13] rust: add basic serial device bus abstractions
> config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260717/202607171517.ScFnGK4R-lkp@intel.com/config)
> compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
> rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260717/202607171517.ScFnGK4R-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202607171517.ScFnGK4R-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
Now dropped, don't worry about this.
prev parent reply other threads:[~2026-07-17 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 13:07 [tty:tty-testing 11/13] error[E0425]: cannot find type `BoundInternal` in module `device` kernel test robot
2026-07-17 13:16 ` 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=2026071755-overture-crunchy-bfaa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=markus.probst@posteo.de \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox