From: Joel Stanley <joel@jms.id.au>
To: Quan Nguyen <quan@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Linux kernel updates and v6.0
Date: Thu, 6 Oct 2022 08:37:38 +0000 [thread overview]
Message-ID: <CACPK8XeOV71erRYS9YkkKJqjUnAPTucC4t1Ltfke6+jkVTrmvA@mail.gmail.com> (raw)
In-Reply-To: <27257597-8068-ab59-ec5d-99deb66065e2@os.amperecomputing.com>
On Thu, 6 Oct 2022 at 07:04, Quan Nguyen <quan@os.amperecomputing.com> wrote:
>
>
> >
> >> Please address any future patches to the dev-6.0 tree.
> >
> > If you have pending patches then please let me know that you want them
> > merged to the dev-6.0 branch. Otherwise, rebase and re-send them to
> > the list.
> >
>
> Hi Joel,
>
> Could you help to pick this patchset to the dev-6.0 branch ?
>
> https://lore.kernel.org/lkml/20221004093106.1653317-4-quan@os.amperecomputing.com/
I merged this but it caused a build error:
drivers/char/ipmi/ssif_bmc.c:864:27: error: initialization of ‘int
(*)(struct i2c_client *)’ from incompatible pointer type ‘void
(*)(struct i2c_client *)’ [-Werror=incompatible-pointer-types]
864 | .remove = ssif_bmc_remove,
| ^~~~~~~~~~~~~~~
I think in 6.1 the i2c drivers will return void in their remove
callbacks, but before then they still need to return an int. I have
updated your change with this patch:
--- a/drivers/char/ipmi/ssif_bmc.c
+++ b/drivers/char/ipmi/ssif_bmc.c
@@ -835,12 +835,14 @@ static int ssif_bmc_probe(struct i2c_client
*client, const struct i2c_device_id
return ret;
}
-static void ssif_bmc_remove(struct i2c_client *client)
+static int ssif_bmc_remove(struct i2c_client *client)
{
struct ssif_bmc_ctx *ssif_bmc = i2c_get_clientdata(client);
i2c_slave_unregister(client);
misc_deregister(&ssif_bmc->miscdev);
+
+ return 0;
}
Cheers,
Joel
next prev parent reply other threads:[~2022-10-06 8:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:34 Linux kernel updates and v6.0 Joel Stanley
2022-09-28 22:30 ` William Kennington
2022-10-05 11:32 ` Patrick Williams
2022-10-24 4:32 ` Joel Stanley
2022-10-06 1:26 ` Joel Stanley
2022-10-06 3:31 ` Patrick Williams
2022-10-06 8:33 ` Joel Stanley
2022-10-06 7:04 ` Quan Nguyen
2022-10-06 8:37 ` Joel Stanley [this message]
2022-10-06 12:52 ` Quan Nguyen
2022-10-24 0:07 ` Tao Ren
2022-10-24 4:31 ` Joel Stanley
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=CACPK8XeOV71erRYS9YkkKJqjUnAPTucC4t1Ltfke6+jkVTrmvA@mail.gmail.com \
--to=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=quan@os.amperecomputing.com \
/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).