On 21.06.17 15:00:25, Robert Richter wrote:
> On 20.06.17 09:49:32, Will Deacon wrote:
> > Hi Robert,
> >
> > On Tue, Jun 20, 2017 at 08:34:39AM +0200, Robert Richter wrote:
> > > On 07.06.17 12:50:12, Will Deacon wrote:
> > >
> > > > Thanks, I've pushed this out as:
> > > >
> > > >
On 20.06.17 09:49:32, Will Deacon wrote:
> Hi Robert,
>
> On Tue, Jun 20, 2017 at 08:34:39AM +0200, Robert Richter wrote:
> > On 07.06.17 12:50:12, Will Deacon wrote:
> >
> > > Thanks, I've pushed this out as:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> > >
Hi Robert,
On Tue, Jun 20, 2017 at 08:34:39AM +0200, Robert Richter wrote:
> On 07.06.17 12:50:12, Will Deacon wrote:
>
> > Thanks, I've pushed this out as:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> > for-next/ras-apei
> >
> > which I'll merge into for-next/core
Will,
On 07.06.17 12:50:12, Will Deacon wrote:
> Thanks, I've pushed this out as:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> for-next/ras-apei
>
> which I'll merge into for-next/core (and therefore linux-next) either the
> end of this week or the beginning of next
On Fri, May 19, 2017 at 02:32:02PM -0600, Tyler Baicar wrote:
> When a memory error, CPU error, PCIe error, or other type of hardware error
> that's covered by RAS occurs, firmware should populate the shared GHES memory
> location with the proper GHES structures to notify the OS of the error.
>
On Fri, May 19, 2017 at 02:32:02PM -0600, Tyler Baicar wrote:
> When a memory error, CPU error, PCIe error, or other type of hardware error
> that's covered by RAS occurs, firmware should populate the shared GHES memory
> location with the proper GHES structures to notify the OS of the error.
...
