From: kernel test robot <lkp@intel.com>
To: Isaku Yamahata <isaku.yamahata@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [intel-tdx:kvm-upstream 53/235] checkpatch: WARNING: Symbolic permissions 'S_IRUSR | S_IWUSR' are not preferred. Consider using octal permissions '0600'.
Date: Thu, 12 Oct 2023 14:09:59 +0800 [thread overview]
Message-ID: <202310121421.THSykYkK-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream
head: 7a3180b27232bff6b95d65874e05272fa0c99b01
commit: 5f1fa54eb9679de954dfbe9aba4887d16d0780d5 [53/235] x86/mce/inject: Add notrigger entry to suppress MCE injection
reproduce: (https://download.01.org/0day-ci/archive/20231012/202310121421.THSykYkK-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/202310121421.THSykYkK-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IRUSR | S_IWUSR' are not preferred. Consider using octal permissions '0600'.
#93: FILE: arch/x86/kernel/cpu/mce/inject.c:739:
+ .perm = S_IRUSR | S_IWUSR },
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-12 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 6:09 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 7:08 [intel-tdx:kvm-upstream 53/235] checkpatch: WARNING: Symbolic permissions 'S_IRUSR | S_IWUSR' are not preferred. Consider using octal permissions '0600' kernel test robot
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=202310121421.THSykYkK-lkp@intel.com \
--to=lkp@intel.com \
--cc=isaku.yamahata@intel.com \
--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 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.