From: ChiaWei Wang <chiawei_wang@aspeedtech.com>
To: "minyard@acm.org" <minyard@acm.org>
Cc: "linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH] ipmi: kcs: aspeed: Update port address comments
Date: Fri, 23 Sep 2022 00:38:08 +0000 [thread overview]
Message-ID: <HK0PR06MB377992E9AF7B91CE41452B4A91519@HK0PR06MB3779.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <Yyz70LckHqyiNhGa@minyard.net>
> From: Corey Minyard <tcminyard@gmail.com> On Behalf Of Corey Minyard
> Sent: Friday, September 23, 2022 8:21 AM
>
> On Fri, Sep 23, 2022 at 12:08:07AM +0000, ChiaWei Wang wrote:
> > Hi Corey,
> >
> > > From: Corey Minyard <tcminyard@gmail.com> On Behalf Of Corey
> Minyard
> > > Sent: Friday, September 23, 2022 2:58 AM
> > >
> > > On Tue, Sep 20, 2022 at 10:03:33AM +0800, Chia-Wei Wang wrote:
> > > > Remove AST_usrGuide_KCS.pdf as it is no longer maintained.
> > >
> > > Even if it's no longer maintained, is it useful? It seems better to
> > > leave in useful documentation unless it has been replaced with something
> else.
> >
> > This document has no permeant public link to access.
> > Aspeed has dropped this file but we keep receiving customer request asking
> for this document.
> > The most important part regarding KCS port rule is still kept in the updated
> comment.
>
> I mean, if you have code that is implementing what is documented, why did
> you remove the document? I don't understand why you would retire
> documentation that people still want to use.
>
> I could put it on the IPMI sourceforge or github page as a historical document.
This document is a personal note of one of our former employee.
It is known to only the owner and his supporting customers.
Most of us has no access to this document.
In addition, after chip revision, certain information is not guaranteed anymore.
Regards,
Chiawei
next prev parent reply other threads:[~2022-09-23 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 2:03 [PATCH] ipmi: kcs: aspeed: Update port address comments Chia-Wei Wang
2022-09-22 18:57 ` Corey Minyard
2022-09-23 0:08 ` ChiaWei Wang
2022-09-23 0:20 ` Corey Minyard
2022-09-23 0:38 ` ChiaWei Wang [this message]
2022-09-23 0:46 ` Corey Minyard
2022-09-23 1:12 ` ChiaWei Wang
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=HK0PR06MB377992E9AF7B91CE41452B4A91519@HK0PR06MB3779.apcprd06.prod.outlook.com \
--to=chiawei_wang@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.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).