From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v3 2/3] dt-bindings: crypto: eip93: add support for Mediatek MT7621 SoC
Date: Sat, 3 Jan 2026 18:12:31 +0100 [thread overview]
Message-ID: <202601031832.ZAAMObxI-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260102155341.3682013-2-olek2@wp.pl>
References: <20260102155341.3682013-2-olek2@wp.pl>
TO: Aleksander Jan Bajkowski <olek2@wp.pl>
TO: benjamin.larsson@genexis.eu
TO: chester.a.unal@arinc9.com
TO: davem@davemloft.net
TO: angelogioacchino.delregno@collabora.com
TO: ansuelsmth@gmail.com
TO: conor+dt@kernel.org
TO: herbert@gondor.apana.org.au
TO: krzk+dt@kernel.org
TO: matthias.bgg@gmail.com
TO: robh@kernel.org
TO: sergio.paracuellos@gmail.com
TO: tsbogend@alpha.franken.de
TO: devicetree@vger.kernel.org
TO: linux-arm-kernel@lists.infradead.org
TO: linux-crypto@vger.kernel.org
TO: linux-kernel@vger.kernel.org
TO: linux-mediatek@lists.infradead.org
TO: linux-mips@vger.kernel.org
CC: Aleksander Jan Bajkowski <olek2@wp.pl>
Hi Aleksander,
kernel test robot noticed the following build warnings:
[auto build test WARNING on herbert-cryptodev-2.6/master]
[also build test WARNING on herbert-crypto-2.6/master robh/for-next linus/master v6.16-rc1 next-20251219]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Aleksander-Jan-Bajkowski/dt-bindings-crypto-eip93-add-support-for-Mediatek-MT7621-SoC/20260102-235536
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
patch link: https://lore.kernel.org/r/20260102155341.3682013-2-olek2%40wp.pl
patch subject: [PATCH v3 2/3] dt-bindings: crypto: eip93: add support for Mediatek MT7621 SoC
:::::: branch date: 25 hours ago
:::::: commit date: 25 hours ago
config: openrisc-randconfig-2052-20260103 (https://download.01.org/0day-ci/archive/20260103/202601031832.ZAAMObxI-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 14.3.0
dtschema version: 2025.12
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260103/202601031832.ZAAMObxI-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/r/202601031832.ZAAMObxI-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml:35:13: [warning] wrong indentation: expected 14 but found 12 (indentation)
vim +35 Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip93.yaml
bbbbd1d149e8b2 Christian Marangi 2025-01-14 8
bbbbd1d149e8b2 Christian Marangi 2025-01-14 9 maintainers:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 10 - Christian Marangi <ansuelsmth@gmail.com>
bbbbd1d149e8b2 Christian Marangi 2025-01-14 11
bbbbd1d149e8b2 Christian Marangi 2025-01-14 12 description: |
bbbbd1d149e8b2 Christian Marangi 2025-01-14 13 The Inside Secure SafeXcel EIP-93 is a cryptographic engine IP block
bbbbd1d149e8b2 Christian Marangi 2025-01-14 14 integrated in varios devices with very different and generic name from
bbbbd1d149e8b2 Christian Marangi 2025-01-14 15 PKTE to simply vendor+EIP93. The real IP under the hood is actually
bbbbd1d149e8b2 Christian Marangi 2025-01-14 16 developed by Inside Secure and given to license to vendors.
bbbbd1d149e8b2 Christian Marangi 2025-01-14 17
bbbbd1d149e8b2 Christian Marangi 2025-01-14 18 The IP block is sold with different model based on what feature are
bbbbd1d149e8b2 Christian Marangi 2025-01-14 19 needed and are identified with the final letter. Each letter correspond
bbbbd1d149e8b2 Christian Marangi 2025-01-14 20 to a specific set of feature and multiple letter reflect the sum of the
bbbbd1d149e8b2 Christian Marangi 2025-01-14 21 feature set.
bbbbd1d149e8b2 Christian Marangi 2025-01-14 22
bbbbd1d149e8b2 Christian Marangi 2025-01-14 23 EIP-93 models:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 24 - EIP-93i: (basic) DES/Triple DES, AES, PRNG, IPsec ESP, SRTP, SHA1
bbbbd1d149e8b2 Christian Marangi 2025-01-14 25 - EIP-93ie: i + SHA224/256, AES-192/256
bbbbd1d149e8b2 Christian Marangi 2025-01-14 26 - EIP-93is: i + SSL/DTLS/DTLS, MD5, ARC4
bbbbd1d149e8b2 Christian Marangi 2025-01-14 27 - EIP-93ies: i + e + s
bbbbd1d149e8b2 Christian Marangi 2025-01-14 28 - EIP-93iw: i + AES-XCB-MAC, AES-CCM
bbbbd1d149e8b2 Christian Marangi 2025-01-14 29
bbbbd1d149e8b2 Christian Marangi 2025-01-14 30 properties:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 31 compatible:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 32 oneOf:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 33 - items:
ea68b16ba9ed87 Aleksander Jan Bajkowski 2026-01-02 34 - enum:
ea68b16ba9ed87 Aleksander Jan Bajkowski 2026-01-02 @35 - airoha,en7581-eip93
ea68b16ba9ed87 Aleksander Jan Bajkowski 2026-01-02 36 - mediatek,mt7621-eip93
bbbbd1d149e8b2 Christian Marangi 2025-01-14 37 - const: inside-secure,safexcel-eip93ies
bbbbd1d149e8b2 Christian Marangi 2025-01-14 38 - items:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 39 - not: {}
bbbbd1d149e8b2 Christian Marangi 2025-01-14 40 description: Need a SoC specific compatible
bbbbd1d149e8b2 Christian Marangi 2025-01-14 41 - enum:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 42 - inside-secure,safexcel-eip93i
bbbbd1d149e8b2 Christian Marangi 2025-01-14 43 - inside-secure,safexcel-eip93ie
bbbbd1d149e8b2 Christian Marangi 2025-01-14 44 - inside-secure,safexcel-eip93is
bbbbd1d149e8b2 Christian Marangi 2025-01-14 45 - inside-secure,safexcel-eip93iw
bbbbd1d149e8b2 Christian Marangi 2025-01-14 46
bbbbd1d149e8b2 Christian Marangi 2025-01-14 47 reg:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 48 maxItems: 1
bbbbd1d149e8b2 Christian Marangi 2025-01-14 49
bbbbd1d149e8b2 Christian Marangi 2025-01-14 50 interrupts:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 51 maxItems: 1
bbbbd1d149e8b2 Christian Marangi 2025-01-14 52
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 53 clocks:
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 54 maxItems: 1
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 55
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 56 resets:
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 57 maxItems: 1
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 58
bbbbd1d149e8b2 Christian Marangi 2025-01-14 59 required:
bbbbd1d149e8b2 Christian Marangi 2025-01-14 60 - compatible
bbbbd1d149e8b2 Christian Marangi 2025-01-14 61 - reg
bbbbd1d149e8b2 Christian Marangi 2025-01-14 62 - interrupts
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 63 - clocks
b36d02ca8cba9c Aleksander Jan Bajkowski 2026-01-02 64 - resets
bbbbd1d149e8b2 Christian Marangi 2025-01-14 65
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-03 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 17:12 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-02 15:47 [PATCH v3 1/3] dt-bindings: crypto: eip93: add clock gate and reset line Aleksander Jan Bajkowski
2026-01-02 15:47 ` [PATCH v3 2/3] dt-bindings: crypto: eip93: add support for Mediatek MT7621 SoC Aleksander Jan Bajkowski
2026-01-02 17:38 ` Rob Herring (Arm)
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=202601031832.ZAAMObxI-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.