On Mon, Jun 23, 2014 at 09:12:32AM -0500, Ken Cox wrote:
>
> On 06/17/2014 05:49 PM, Greg KH wrote:
> >On Tue, Jun 03, 2014 at 09:43:35AM -0500, Ken Cox wrote:
> >>The unisys drivers now properly check to make sure they are running
> >>on the s-Par platform before they will initialize. This was f
On 06/17/2014 05:49 PM, Greg KH wrote:
On Tue, Jun 03, 2014 at 09:43:35AM -0500, Ken Cox wrote:
The unisys drivers now properly check to make sure they are running
on the s-Par platform before they will initialize. This was fixed in
commit fcd0157ece so it is safe to allow the unisys drivers t
On Tue, Jun 03, 2014 at 09:43:35AM -0500, Ken Cox wrote:
> The unisys drivers now properly check to make sure they are running
> on the s-Par platform before they will initialize. This was fixed in
> commit fcd0157ece so it is safe to allow the unisys drivers to be built.
>
> This has been tested
On Tue, Jun 03, 2014 at 09:43:35AM -0500, Ken Cox wrote:
> The unisys drivers now properly check to make sure they are running
> on the s-Par platform before they will initialize. This was fixed in
> commit fcd0157ece so it is safe to allow the unisys drivers to be built.
>
> This has been tested
The unisys drivers now properly check to make sure they are running
on the s-Par platform before they will initialize. This was fixed in
commit fcd0157ece so it is safe to allow the unisys drivers to be built.
This has been tested in the same qemu environment that originally
produced the panic an
