From: Akira shimahara <akira215corp@gmail.com>
To: Evgeniy Polyakov <zbr@ioremap.net>, Greg KH <greg@kroah.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Changes in w1_therm.c and adding w1_therm.h
Date: Thu, 23 Apr 2020 19:59:18 +0200 [thread overview]
Message-ID: <32dbb39debedabd6dbd1a8675760e171c180de9e.camel@gmail.com> (raw)
In-Reply-To: <307231587661588@mail.yandex.ru>
Le jeudi 23 avril 2020 à 20:07 +0300, Evgeniy Polyakov a écrit :
> Hi
>
> 23.04.2020, 17:41, "Greg KH" <greg@kroah.com>:
> > You do not document any of these new sysfs files, why not?
>
> Looks like there are bigger isues with the patch that I've missed,
> and if I understood correctly, Akira asked to drop this patch
Hi,
Evgeniy, I don't asked to drop this patch, sorry for the
misunderstanding. I will add entries to Documentation/ABI/testing/ by
the end of the week and submit a new patch. Who should I add in the
'Contact' field ?
To answer Greg's comments, we use the kernel subsystems as much as
possible, but for timing and bus protocol reasons, we have to go a
little deeper and control bus transaction as close as possible.
Evgeniy, could you detail the issues you are talking about so I can
adjust if required ?
Thanks again for you time, regards
Akira Shimahara
next prev parent reply other threads:[~2020-04-23 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 17:02 [PATCH] Changes in w1_therm.c and adding w1_therm.h Akira Shimahara
2020-04-16 20:12 ` Evgeniy Polyakov
2020-04-17 13:04 ` akira215
2020-04-23 14:41 ` Greg KH
2020-04-23 17:07 ` Evgeniy Polyakov
2020-04-23 17:59 ` Akira shimahara [this message]
2020-04-23 18:16 ` Evgeniy Polyakov
2020-04-25 15:31 ` [PATCH v2 1/2] " Akira Shimahara
2020-04-26 7:51 ` Greg KH
2020-04-26 12:36 ` Akira shimahara
2020-04-26 17:09 ` Greg KH
2020-04-26 17:20 ` Akira shimahara
2020-04-28 12:44 ` Greg KH
2020-04-28 13:42 ` Akira shimahara
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=32dbb39debedabd6dbd1a8675760e171c180de9e.camel@gmail.com \
--to=akira215corp@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zbr@ioremap.net \
/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