From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>,
Paul Burton <paul.burton@imgtec.com>, <linux-mips@linux-mips.org>
Subject: Re: [PATCH] MIPS: Fix errata for some 1074K cores.
Date: Thu, 12 Sep 2013 11:02:15 -0500 [thread overview]
Message-ID: <5231E587.9030403@imgtec.com> (raw)
In-Reply-To: <CAGVrzcYxyWv2F1HDkOUCo2Ezicxq+UsxouOsUtz+UZAWFew18A@mail.gmail.com>
On 09/12/2013 10:50 AM, Florian Fainelli wrote:
>
> Are there any reasons why you cannot quote an internal note about this
> errata which would give a better idea of what this code is about?
> Sorry but the diff really does not help understand what is happening
> without a proper explanation of why this is required. At first glance
> it would like some revisions of the CPU are affected by some D$ bug?
>
Okaaay. How about we just stop here. I posted a poor quality patch that
did not have enough information. I will post a second version that will
have the details of what E16 is and what is being fixed. This will
involve me talking to hardware engineers to get something I can put in
the patch. My sincere apologies to everyone. I will go crawl back under
my rock and finish my work for this week. You should see the corrected
version the first part of next week. Cheers.
Steve
WARNING: multiple messages have this Message-ID (diff)
From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>,
Paul Burton <paul.burton@imgtec.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Fix errata for some 1074K cores.
Date: Thu, 12 Sep 2013 11:02:15 -0500 [thread overview]
Message-ID: <5231E587.9030403@imgtec.com> (raw)
Message-ID: <20130912160215.zrJZoy3ija-0PYy9FfUcpW5mWMtfiBPsGgv7LgjUjVc@z> (raw)
In-Reply-To: <CAGVrzcYxyWv2F1HDkOUCo2Ezicxq+UsxouOsUtz+UZAWFew18A@mail.gmail.com>
On 09/12/2013 10:50 AM, Florian Fainelli wrote:
>
> Are there any reasons why you cannot quote an internal note about this
> errata which would give a better idea of what this code is about?
> Sorry but the diff really does not help understand what is happening
> without a proper explanation of why this is required. At first glance
> it would like some revisions of the CPU are affected by some D$ bug?
>
Okaaay. How about we just stop here. I posted a poor quality patch that
did not have enough information. I will post a second version that will
have the details of what E16 is and what is being fixed. This will
involve me talking to hardware engineers to get something I can put in
the patch. My sincere apologies to everyone. I will go crawl back under
my rock and finish my work for this week. You should see the corrected
version the first part of next week. Cheers.
Steve
next prev parent reply other threads:[~2013-09-12 16:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 20:01 [PATCH] MIPS: Fix errata for some 1074K cores Steven J. Hill
2013-09-12 9:39 ` Paul Burton
2013-09-12 9:39 ` Paul Burton
2013-09-12 14:57 ` Leonid Yegoshin
2013-09-12 15:05 ` Florian Fainelli
2013-09-12 15:12 ` Leonid Yegoshin
2013-09-12 15:12 ` Paul Burton
2013-09-12 15:30 ` Leonid Yegoshin
2013-09-12 15:50 ` Florian Fainelli
2013-09-12 16:02 ` Steven J. Hill [this message]
2013-09-12 16:02 ` Steven J. Hill
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=5231E587.9030403@imgtec.com \
--to=steven.hill@imgtec.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=f.fainelli@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.