From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alexandre Bounine <alexandre.bounine@idt.com>,
Matt Porter <mporter@kernel.crashing.org>
Subject: [PROBLEM linux-next]
Date: Tue, 9 Jul 2024 23:14:51 +0200 [thread overview]
Message-ID: <06099367-4da5-4777-aace-b5acddbad7b8@gmail.com> (raw)
Dear all,
On the linux-next vanilla next-20240709 tree, I have attempted the seed KCONFIG_SEED=0xEE7AB52F
which was known from before to trigger various errors in compile and build process.
Though this might seem as contributing to channel noise, Linux refuses to build this config,
treating warnings as errors, using this build line:
$ time nice make W=1 -k -j 36 |& tee ../err-next-20230709-01a.log; date
As I know that the Chief Penguin doesn't like warnings, but I am also aware that there are plenty
left, there seems to be more tedious work ahead to make the compilers happy.
The compiler output is:
drivers/rapidio/rio_cm.c: In function ‘rio_txcq_handler’:
drivers/rapidio/rio_cm.c:675:21: error: variable ‘rc’ set but not used [-Werror=unused-but-set-variable]
675 | int rc;
| ^~
cc1: all warnings being treated as errors
670 /*
671 * If there are pending requests, insert them into transmit queue
672 */
673 if (!list_empty(&cm->tx_reqs) && (cm->tx_cnt < RIOCM_TX_RING_SIZE)) {
674 struct tx_req *req, *_req;
→ 675 int rc;
676
677 list_for_each_entry_safe(req, _req, &cm->tx_reqs, node) {
678 list_del(&req->node);
679 cm->tx_buf[cm->tx_slot] = req->buffer;
→ 680 rc = rio_add_outb_message(cm->mport, req->rdev, cmbox,
681 req->buffer, req->len);
682 kfree(req->buffer);
683 kfree(req);
684
685 ++cm->tx_cnt;
686 ++cm->tx_slot;
687 cm->tx_slot &= (RIOCM_TX_RING_SIZE - 1);
688 if (cm->tx_cnt == RIOCM_TX_RING_SIZE)
689 break;
690 }
691 }
692
693 spin_unlock(&cm->tx_lock);
694 }
Hope this helps.
Best regards,
Mirsad Todorovac
next reply other threads:[~2024-07-09 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 21:14 Mirsad Todorovac [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-07 0:10 [PROBLEM linux-next] Mirsad Todorovac
2024-07-07 7:37 ` Rafał Miłecki
2024-07-07 8:12 ` Jonas Gorski
2024-07-07 14:09 ` Mirsad Todorovac
2024-07-07 14:45 ` Mirsad Todorovac
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=06099367-4da5-4777-aace-b5acddbad7b8@gmail.com \
--to=mtodorovac69@gmail.com \
--cc=alexandre.bounine@idt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.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