From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Richard Weinberger" <richard@nod.at>
Cc: "kernel test robot" <lkp@intel.com>,
"david" <david@sigma-star.at>,
"oe-kbuild-all" <oe-kbuild-all@lists.linux.dev>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"david oberhollenzer" <david.oberhollenzer@sigma-star.at>
Subject: Re: security/keys/trusted-keys/trusted_dcp.c:206:24: sparse: sparse: incorrect type in assignment (different base types)
Date: Sat, 25 May 2024 01:21:34 +0300 [thread overview]
Message-ID: <D1I84BEOGWMW.25XO15A34Y8J2@kernel.org> (raw)
In-Reply-To: <39518719.144820.1716586062550.JavaMail.zimbra@nod.at>
On Sat May 25, 2024 at 12:27 AM EEST, Richard Weinberger wrote:
> > Please send then fix, reasoning of that, and finally:
> Sure. Let me first talk to David and give it a test...
No rush
BR, Jarkko
prev parent reply other threads:[~2024-05-24 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 22:48 security/keys/trusted-keys/trusted_dcp.c:206:24: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2024-05-24 21:06 ` Richard Weinberger
2024-05-24 21:24 ` Jarkko Sakkinen
2024-05-24 21:27 ` Richard Weinberger
2024-05-24 22:21 ` Jarkko Sakkinen [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=D1I84BEOGWMW.25XO15A34Y8J2@kernel.org \
--to=jarkko@kernel.org \
--cc=david.oberhollenzer@sigma-star.at \
--cc=david@sigma-star.at \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
/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