From: Dmitry Khromov <dk@icelogic.net>
To: Greg KH <gregkh@linuxfoundation.org>, Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH v2] w1: introduce an ability to specify microseconds bus scanning intervals
Date: Thu, 23 Apr 2015 14:30:50 +0300 [thread overview]
Message-ID: <5538D7EA.30403@icelogic.net> (raw)
In-Reply-To: <20150423092040.GB19457@kroah.com>
On 23.04.2015 12:20, Greg KH wrote:
> On Thu, Apr 23, 2015 at 12:55:35AM +0300, Dmitry Khromov wrote:
>> Signed-off-by: Dmitry Khromov <dk@icelogic.net>
>> ---
>> drivers/w1/w1.c | 17 ++++++++++++++++-
>> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> You added a new sysfs file, without any documentation about it added to
> Documentation/ABI, nor any reason why this needs to be done in the
> changelog entry for the patch.
Sorry for that, the complete reason was given in the original version of
the patch, I've added a short summary in the changelog for v3. Thanks
for reminding about the documentation. I've added a short description
and minor cosmetics to Documentation/w1/w1.generic to give a slightly
more detailed idea on what's going on during the bus scan.
Please review.
--
Regards,
- Dmitry
next prev parent reply other threads:[~2015-04-23 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55292A69.5020106@icelogic.net>
[not found] ` <1040571428797306@web8j.yandex.ru>
2015-04-14 7:40 ` [PATCH] Introduce an ability to specify microseconds bus scanning intervals in w1 core Dmitry Khromov
2015-04-14 17:15 ` Randy Dunlap
2015-04-22 21:55 ` [PATCH v2] w1: introduce an ability to specify microseconds bus scanning intervals Dmitry Khromov
2015-04-22 23:22 ` Evgeniy Polyakov
2015-04-23 9:20 ` Greg KH
2015-04-23 11:30 ` Dmitry Khromov [this message]
2015-04-23 11:33 ` [PATCH v3] " Dmitry Khromov
2015-05-12 19:29 ` Dmitry Khromov
2015-05-13 15:00 ` Evgeniy Polyakov
2015-05-13 15:31 ` gregkh
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=5538D7EA.30403@icelogic.net \
--to=dk@icelogic.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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