lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <HK0PR06MB377992E9AF7B91CE41452B4A91519@HK0PR06MB3779.apcprd06.prod.outlook.com>
Date:   Fri, 23 Sep 2022 00:38:08 +0000
From:   ChiaWei Wang <chiawei_wang@...eedtech.com>
To:     "minyard@....org" <minyard@....org>
CC:     "joel@....id.au" <joel@....id.au>,
        "andrew@...id.au" <andrew@...id.au>,
        "openipmi-developer@...ts.sourceforge.net" 
        <openipmi-developer@...ts.sourceforge.net>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>
Subject: RE: [PATCH] ipmi: kcs: aspeed: Update port address comments

> From: Corey Minyard <tcminyard@...il.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@...il.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ