automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, Andrew.Rybchenko@oktetlabs.ru
Subject: [dpdk-test-report] |WARNING| pw(112332) sid(23257) job(PER_PATCH_BUILD2870)[v3, 2/2] kni: fix warning about discarding const qualifier
Date: 05 Jun 2022 02:57:52 -0700	[thread overview]
Message-ID: <003cea$i4068h@orsmga008-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2740 bytes --]


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/112332

_apply issues_

Submitter: Andrew Rybchenko <Andrew.Rybchenko@oktetlabs.ru>
Date: 2022-06-05 09:47:14
Reply_mail: <20220605094714.3286158-2-andrew.rybchenko@oktetlabs.ru>

DPDK git baseline:
	Repo:dpdk-next-net, CommitID: c591e611b289301651234d69f2942cf1d17d6fdd
	Repo:dpdk, CommitID: eadc35df59a1a1a5017c0db1c7a9978ca8eb56e9


* Repo: dpdk-next-net
releases and call the appropriate function in kni_net.
    
    netif_rx_ni() must be used on older kernel since netif_rx() might
    might lead to deadlocks or other problems there.
    
    Cc: stable@dpdk.org
    
--
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: kernel/linux/kni/kni_misc.c:402
error: kernel/linux/kni/kni_misc.c: patch does not apply
error: patch failed: kernel/linux/kni/kni_net.c:783
error: kernel/linux/kni/kni_net.c: patch does not apply
Applying: examples/kni: clear warning about discarding const qualifier
Applying: kni: fix warning about discarding const qualifier
Patch failed at 0002 kni: fix warning about discarding const qualifier
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

* Repo: dpdk
"n_xstats != n_xstats_names => skipping"
    
    - Invert the check for mlx5_os_read_dev_stat(), currently leading
      us to store the result if the function failed, and use a
      backup value if it succeeded, which is the opposite of what we
      actually want. Revert to the original (correct) test.
    
--
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: kernel/linux/kni/compat.h:145
error: kernel/linux/kni/compat.h: patch does not apply
error: patch failed: kernel/linux/kni/kni_misc.c:402
error: kernel/linux/kni/kni_misc.c: patch does not apply
error: patch failed: kernel/linux/kni/kni_net.c:783
error: kernel/linux/kni/kni_net.c: patch does not apply
Applying: examples/kni: clear warning about discarding const qualifier
Applying: kni: fix warning about discarding const qualifier
Patch failed at 0002 kni: fix warning about discarding const qualifier
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team

                 reply	other threads:[~2022-06-05  9:57 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='003cea$i4068h@orsmga008-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=Andrew.Rybchenko@oktetlabs.ru \
    --cc=test-report@dpdk.org \
    /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;
as well as URLs for NNTP newsgroup(s).