All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jenkins <jenkins@linuxtv.org>
To: mchehab+samsung@kernel.org, linux-media@vger.kernel.org
Cc: builder@linuxtv.org
Subject: Re: [GIT PULL FOR v5.19] cec: various fixes and enhancements (#82257)
Date: Wed,  6 Apr 2022 15:01:39 +0000	[thread overview]
Message-ID: <20220406150139.2013371-1-jenkins@linuxtv.org> (raw)
In-Reply-To: <3f54b8d2-9c26-1775-0cc9-688a677776eb@xs4all.nl>

From: builder@linuxtv.org

Pull request: https://patchwork.linuxtv.org/project/linux-media/patch/3f54b8d2-9c26-1775-0cc9-688a677776eb@xs4all.nl/
Build log: https://builder.linuxtv.org/job/patchwork/197361/
Build time: 00:24:12
Link: https://lore.kernel.org/linux-media/3f54b8d2-9c26-1775-0cc9-688a677776eb@xs4all.nl

gpg: Signature made Wed 06 Apr 2022 10:52:37 AM UTC
gpg:                using EDDSA key 52ADCAAE8A4F70B99ACD8D726B425DF79B1C1E76
gpg: Can't check signature: No public key

Summary: got 2/7 patches with issues, being 1 at build time, plus one error when buinding PDF document

Error/warnings:

patches/0001-cec-call-enable_adap-on-s_log_addrs.patch:

    allyesconfig: return code #0:
	../scripts/genksyms/parse.y: warning: 9 shift/reduce conflicts [-Wconflicts-sr]
	../scripts/genksyms/parse.y: warning: 5 reduce/reduce conflicts [-Wconflicts-rr]
	../scripts/genksyms/parse.y: note: rerun with option '-Wcounterexamples' to generate conflict counterexamples

    allyesconfig: return code #0:
	../drivers/media/test-drivers/vivid/vivid-core.c: ../drivers/media/test-drivers/vivid/vivid-core.c:1983 vivid_create_instance() parse error: turning off implications after 60 seconds
	SMATCH:../drivers/media/usb/siano/smsusb.c ../drivers/media/usb/siano/smsusb.c:53:38: :warning: array of flexible structures
	SPARSE:../drivers/media/usb/siano/smsusb.c ../drivers/media/usb/siano/smsusb.c:53:38: warning: array of flexible structures
	../drivers/media/pci/cx23885/cx23885-dvb.c: ../drivers/media/pci/cx23885/cx23885-dvb.c:2625 dvb_register() parse error: turning off implications after 60 seconds
	../drivers/media/platform/qcom/venus/helpers.c: ../drivers/media/platform/qcom/venus/helpers.c:658 venus_helper_get_bufreq() error: we previously assumed 'req' could be null (see line 654)
	../drivers/media/usb/em28xx/em28xx-video.c: ../drivers/media/usb/em28xx/em28xx-video.c:2900 em28xx_v4l2_init() parse error: turning off implications after 60 seconds

patches/0005-cec-use-call_op-and-check-for-unregistered.patch:

   checkpatch.pl:
	$ cat patches/0005-cec-use-call_op-and-check-for-unregistered.patch | formail -c | ./scripts/checkpatch.pl --terse --mailback --no-summary --strict
	-:173: CHECK: Macro argument reuse 'pin' - possible side-effects?
	-:173: CHECK: Macro argument 'pin' may be better as '(pin)' to avoid precedence issues
	-:173: CHECK: Macro argument reuse 'op' - possible side-effects?
	-:173: CHECK: Macro argument 'op' may be better as '(op)' to avoid precedence issues
	-:177: CHECK: Macro argument reuse 'pin' - possible side-effects?
	-:177: CHECK: Macro argument 'pin' may be better as '(pin)' to avoid precedence issues
	-:177: CHECK: Macro argument reuse 'op' - possible side-effects?
	-:177: CHECK: Macro argument 'op' may be better as '(op)' to avoid precedence issues
	-:290: CHECK: Macro argument reuse 'adap' - possible side-effects?
	-:290: CHECK: Macro argument 'adap' may be better as '(adap)' to avoid precedence issues
	-:290: CHECK: Macro argument reuse 'op' - possible side-effects?
	-:290: CHECK: Macro argument 'op' may be better as '(op)' to avoid precedence issues
	-:294: CHECK: Macro argument reuse 'adap' - possible side-effects?
	-:294: CHECK: Macro argument 'adap' may be better as '(adap)' to avoid precedence issues
	-:294: CHECK: Macro argument reuse 'op' - possible side-effects?
	-:294: CHECK: Macro argument 'op' may be better as '(op)' to avoid precedence issues


Error #512 when building PDF docs


      reply	other threads:[~2022-04-06 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 11:00 [GIT PULL FOR v5.19] cec: various fixes and enhancements Hans Verkuil
2022-04-06 15:01 ` Jenkins [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=20220406150139.2013371-1-jenkins@linuxtv.org \
    --to=jenkins@linuxtv.org \
    --cc=builder@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+samsung@kernel.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 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.