All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tarun Sahu <tarunsahu@google.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: Warning: kernel/liveupdate/luo_file.c:169 struct member '' not described in 'luo_file'
Date: Wed, 01 Jul 2026 08:41:26 +0200	[thread overview]
Message-ID: <202607010856.DQ707tKA-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Tarun-Sahu/mm-memfd_luo-validate-serialized_data-before-conversion/20260629-114451
head:   5893388634f6d17d0a4b1804f95f64bc359e4b4f
commit: 5893388634f6d17d0a4b1804f95f64bc359e4b4f luo: Update serialized data to use KHOSER_PTR
date:   2 days ago
config: x86_64-rhel-9.4-kselftests (https://download.01.org/0day-ci/archive/20260701/202607010856.DQ707tKA-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260701/202607010856.DQ707tKA-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/202607010856.DQ707tKA-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: kernel/liveupdate/luo_file.c:169 struct member '' not described in 'luo_file'
>> Warning: kernel/liveupdate/luo_file.c:169 struct member '' not described in 'luo_file'

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-01  6:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202607010856.DQ707tKA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tarunsahu@google.com \
    /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.