From: Evgeniy Polyakov <zbr@ioremap.net>
To: Ingo Flaschberger <ingo.flaschberger@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] 1wire: family module autoload fails because of upper/lower case mismatch.
Date: Tue, 01 May 2018 21:54:37 +0300 [thread overview]
Message-ID: <5841141525200877@web25j.yandex.ru> (raw)
In-Reply-To: <629ce39b-e3ad-1a4a-be11-7eb3da064ce6@gmail.com>
Hi Ingo
Sorry for late reply and because of forcing you to resend the patch, your changes are correct
01.05.2018, 17:10, "Ingo Flaschberger" <ingo.flaschberger@gmail.com>:
> 1wire family module autoload fails because of upper/lower
> case mismatch.
>
> Signed-off-by: Ingo Flaschberger <ingo.flaschberger@gmail.com>
Greg, please pull this patch into your tree.
Should it be stable material?
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
> ---
> drivers/w1/w1.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/w1/w1.c b/drivers/w1/w1.c
> index ab0931e..aa458f2 100644
> --- a/drivers/w1/w1.c
> +++ b/drivers/w1/w1.c
> @@ -741,7 +741,7 @@ int w1_attach_slave_device(struct w1_master *dev,
> struct w1_reg_num *rn)
>
> /* slave modules need to be loaded in a context with unlocked
> mutex */
> mutex_unlock(&dev->mutex);
> - request_module("w1-family-0x%02x", rn->family);
> + request_module("w1-family-0x%02X", rn->family);
> mutex_lock(&dev->mutex);
>
> spin_lock(&w1_flock);
> --
> 2.7.4
next prev parent reply other threads:[~2018-05-01 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 14:10 [PATCH] 1wire: family module autoload fails because of upper/lower case mismatch Ingo Flaschberger
2018-05-01 18:54 ` Evgeniy Polyakov [this message]
2018-05-01 18:58 ` gregkh
-- strict thread matches above, loose matches on Subject: below --
2018-04-12 0:20 [PATCH] 1wire: family module autoload fails because of upper/lower, " Ingo Flaschberger
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=5841141525200877@web25j.yandex.ru \
--to=zbr@ioremap.net \
--cc=gregkh@linuxfoundation.org \
--cc=ingo.flaschberger@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.