From: Jonathan Corbet <corbet@lwn.net>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Gergo Huszty <huszty.gergo@digitaltrip.hu>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fixed typo in onewire generic doc
Date: Mon, 9 Apr 2018 06:24:22 -0600 [thread overview]
Message-ID: <20180409062422.40423c00@lwn.net> (raw)
In-Reply-To: <6472401523231809@web57o.yandex.ru>
On Mon, 09 Apr 2018 02:56:49 +0300
Evgeniy Polyakov <zbr@ioremap.net> wrote:
> Hi everyone
>
> I'm really sorry for that long delay.
>
> Was this patch accepted or should I push it upstream?
>
> 20.12.2017, 22:09, "Gergo Huszty" <huszty.gergo@digitaltrip.hu>:
> > Onewire devices has 6 byte long unique serial numbers, 1 byte family
> > code and 1 byte CRC. Linux sysfs presents the device folder in the
> > form of familyID-deviceID, so CRC is not shown. The consequence is
> > that the device serial number is always a 12 long hex-string, but
> > doc says 13 in one place. This is corrected by this change.
> > Reference: https://en.wikipedia.org/wiki/1-Wire
Commit d6f44b3bd870ff5946fcd4293b4c07029d8d93c9, merged for 4.16.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-04-09 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171220190709.6584-1-huszty.gergo@digitaltrip.hu>
2018-04-08 23:56 ` [PATCH] Fixed typo in onewire generic doc Evgeniy Polyakov
2018-04-09 12:24 ` Jonathan Corbet [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=20180409062422.40423c00@lwn.net \
--to=corbet@lwn.net \
--cc=huszty.gergo@digitaltrip.hu \
--cc=linux-doc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).