From: Orlando Chamberlain <orlandoch.dev@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Gross <markgross@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the drivers-x86 tree
Date: Thu, 9 Mar 2023 21:40:32 +1100 [thread overview]
Message-ID: <20230309214032.3683db01@redecorated-mbp> (raw)
In-Reply-To: <4c63d660-1105-9a8a-1010-cc05125d06d3@redhat.com>
On Thu, 9 Mar 2023 09:48:58 +0100
Hans de Goede <hdegoede@redhat.com> wrote:
> Hi all,
>
> On 3/9/23 02:28, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the drivers-x86 tree, today's linux-next build
> > (htmldocs) produced these warning:
> >
> > include/linux/apple-gmux.h:99: warning: Function parameter or
> > member 'type_ret' not described in 'apple_gmux_detect'
> > include/linux/apple-gmux.h:99: warning: Excess function parameter
> > 'indexed_ret' description in 'apple_gmux_detect'
> >
> > Introduced by commit
> >
> > fc83fbc80e1a ("platform/x86: apple-gmux: refactor gmux types")
Thanks Stephen.
>
> Stephen, thank you for reporting this.
>
> Orlando, can you do a follow-up patch on top of your
> latest series fixing this ?
Yes, I'll send one soon.
>
> Regards,
>
> Hans
>
next prev parent reply other threads:[~2023-03-09 10:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 1:28 linux-next: build warnings after merge of the drivers-x86 tree Stephen Rothwell
2023-03-09 8:48 ` Hans de Goede
2023-03-09 10:40 ` Orlando Chamberlain [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-22 2:54 Stephen Rothwell
2023-12-22 14:10 ` Hans de Goede
2022-03-01 9:16 Stephen Rothwell
2022-03-01 13:53 ` Hans de Goede
2022-03-24 7:33 ` Stephen Rothwell
2022-03-24 7:39 ` Hans de Goede
2022-03-24 11:22 ` Stephen Rothwell
2022-03-24 13:01 ` Hans de Goede
2022-03-24 13:04 ` Hans de Goede
2022-03-24 21:55 ` Stephen Rothwell
2022-03-25 5:27 ` Mauro Carvalho Chehab
2022-03-25 6:18 ` Mauro Carvalho Chehab
2021-10-21 7:47 Stephen Rothwell
2021-10-21 9:07 ` Vadim Pasternak
2021-10-21 20:04 ` Stephen Rothwell
2021-10-21 21:10 ` Jonathan Corbet
2021-10-22 9:02 ` Hans de Goede
2021-10-21 9:14 ` Hans de Goede
2021-10-21 20:02 ` Stephen Rothwell
2020-11-05 6:55 Stephen Rothwell
2011-02-22 5:13 Stephen Rothwell
2011-02-22 10:36 ` Colin Ian King
2010-12-08 2:32 Stephen Rothwell
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=20230309214032.3683db01@redecorated-mbp \
--to=orlandoch.dev@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).