mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: Kalle Valo <kvalo@kernel.org>, linux-wireless@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.4
Date: Mon, 26 Jun 2023 10:24:18 +0200 (CEST)	[thread overview]
Message-ID: <39abf2c7-24a-f167-91da-ed4c5435d1c4@linux-m68k.org> (raw)
In-Reply-To: <20230626081950.2090627-1-geert@linux-m68k.org>

On Mon, 26 Jun 2023, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.4[1] to v6.4-rc7[3], the summaries are:
>  - build errors: +1/-0

   + /kisskb/src/drivers/net/wireless/cisco/airo.c: error: 'status_rid.currentXmitRate' is used uninitialized [-Werror=uninitialized]:  => 6163:45

sh4-gcc11/sh-allmodconfig
seen before

This is actually a real issue, and it's been here since basically forever.

drivers/net/wireless/cisco/airo.c:

     static int airo_get_rate(struct net_device *dev,
                              struct iw_request_info *info,
                              union iwreq_data *wrqu,
                              char *extra)
     {
             struct iw_param *vwrq = &wrqu->bitrate;
             struct airo_info *local = dev->ml_priv;
             StatusRid status_rid;           /* Card status info */

             readStatusRid(local, &status_rid, 1);

==>         vwrq->value = le16_to_cpu(status_rid.currentXmitRate) * 500000;
             ...
     }

     static int readStatusRid(struct airo_info *ai, StatusRid *statr, int lock)
     {
             return PC4500_readrid(ai, RID_STATUS, statr, sizeof(*statr), lock);
     }

     static int PC4500_readrid(struct airo_info *ai, u16 rid, void *pBuf, int len, int lock)
     {
             u16 status;
             int rc = SUCCESS;

             if (lock) {
                     if (down_interruptible(&ai->sem))
                             return ERROR;

pBuf output buffer contents not initialized.

             }
             ...
     }


> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/6995e2de6891c724bfeb2db33d7b87775f913ad1/ (all 160 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/45a3e24f65e90a047bef86f927ebdc4c710edaa1/ (all 160 configs)

Gr{oetje,eeting}s,

 						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
 							    -- Linus Torvalds

  reply	other threads:[~2023-06-26  8:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 23:40 Linux 6.4 Linus Torvalds
2023-06-26  5:39 ` Guenter Roeck
2023-06-26  8:19 ` Build regressions/improvements in v6.4 Geert Uytterhoeven
2023-06-26  8:24   ` Geert Uytterhoeven [this message]
2023-07-09  2:45     ` Build regressions/improvements in v6.4 (wireless/airo) Randy Dunlap
2023-07-09  7:38       ` John Paul Adrian Glaubitz
2023-07-09 13:09         ` Randy Dunlap
2023-07-09  8:27       ` Geert Uytterhoeven
2023-07-09 13:12         ` Randy Dunlap
2023-07-09 13:23           ` Geert Uytterhoeven
2023-07-09 13:26             ` Randy Dunlap

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=39abf2c7-24a-f167-91da-ed4c5435d1c4@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®