From: Corey Minyard <minyard@acm.org>
To: Tang Bin <tangbin@cmss.chinamobile.com>
Cc: arnd@arndb.de, gregkh@linuxfoundation.org,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Shengju Zhang <zhangshengju@cmss.chinamobile.com>
Subject: Re: [PATCH] ipmi:bt-bmc: Fix some format issue of the code
Date: Tue, 14 Apr 2020 14:41:53 -0500 [thread overview]
Message-ID: <20200414194153.GG3587@minyard.net> (raw)
In-Reply-To: <20200414141814.19048-1-tangbin@cmss.chinamobile.com>
On Tue, Apr 14, 2020 at 10:18:14PM +0800, Tang Bin wrote:
> Fix some format issue of the code in bt-bmc.c
Applied, thanks.
-corey
>
> Signed-off-by: Tang Bin <tangbin@cmss.chinamobile.com>
> Signed-off-by: Shengju Zhang <zhangshengju@cmss.chinamobile.com>
> ---
> drivers/char/ipmi/bt-bmc.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/char/ipmi/bt-bmc.c b/drivers/char/ipmi/bt-bmc.c
> index 890ad55aa..cd0349bff 100644
> --- a/drivers/char/ipmi/bt-bmc.c
> +++ b/drivers/char/ipmi/bt-bmc.c
> @@ -463,9 +463,9 @@ static int bt_bmc_probe(struct platform_device *pdev)
> init_waitqueue_head(&bt_bmc->queue);
>
> bt_bmc->miscdev.minor = MISC_DYNAMIC_MINOR,
> - bt_bmc->miscdev.name = DEVICE_NAME,
> - bt_bmc->miscdev.fops = &bt_bmc_fops,
> - bt_bmc->miscdev.parent = dev;
> + bt_bmc->miscdev.name = DEVICE_NAME,
> + bt_bmc->miscdev.fops = &bt_bmc_fops,
> + bt_bmc->miscdev.parent = dev;
> rc = misc_register(&bt_bmc->miscdev);
> if (rc) {
> dev_err(dev, "Unable to register misc device\n");
> --
> 2.20.1.windows.1
>
>
>
prev parent reply other threads:[~2020-04-14 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 14:18 [PATCH] ipmi:bt-bmc: Fix some format issue of the code Tang Bin
2020-04-14 19:41 ` Corey Minyard [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=20200414194153.GG3587@minyard.net \
--to=minyard@acm.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=tangbin@cmss.chinamobile.com \
--cc=zhangshengju@cmss.chinamobile.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).