From: Deep Majumder <deep@fastmail.in>
To: Wolfram Sang <wsa@kernel.org>,
linux-doc@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Docs: Fixes link to I2C specification
Date: Fri, 12 Nov 2021 00:13:07 +0530 [thread overview]
Message-ID: <20211111184307.6ld75ektg6avb3wb@pop-os.localdomain> (raw)
In-Reply-To: <YYWqGyETMgKcIkul@kunai>
Wolfram Sang wrote:
> On Thu, Nov 04, 2021 at 11:30:18AM +0530, Deep Majumder wrote:
> > The link to the I2C specification is broken and is replaced in this
> > patch by one that points to Rev 6 (2014) of the specification.
> > Although `https://www.nxp.com" hosts the Rev 7 (2021) of this
> > specification, it is behind a login-wall and thus cannot be used.
> >
> > Signed-off-by: Deep Majumder <deep@fastmail.in>
>
> Thanks for pointing out this issue!
>
> > The official I2C specification is the `"I2C-bus specification and user
> > -manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_
> > +manual" (UM10204) <https://www.pololu.com/file/0J435/UM10204.pdf>`_
>
> I'd think we should have two links. One to the latest official specs,
> even though it is behind a login wall. And one to the latest free
> version. For that, I think the archieve.org address which Wikipedia uses
> is more stable thant the pololu address from above:
>
> https://web.archive.org/web/20210813122132/https://www.nxp.com/docs/en/user-guide/UM10204.pdf
>
> What do you think?
>
Yes, I agree. Should I update the patch and re-send it?
next prev parent reply other threads:[~2021-11-11 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 6:00 [PATCH] Docs: Fixes link to I2C specification Deep Majumder
2021-11-04 15:20 ` Randy Dunlap
2021-11-05 22:03 ` Wolfram Sang
2021-11-11 18:43 ` Deep Majumder [this message]
2021-11-11 19:36 ` Wolfram Sang
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=20211111184307.6ld75ektg6avb3wb@pop-os.localdomain \
--to=deep@fastmail.in \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@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 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).