Hi Chris,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.14-rc4 next-20171009]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Chris,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.14-rc4 next-20171009]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Tue, Oct 10, 2017 at 12:58 PM, Leif Lindholm
wrote:
>
> On Tue, Oct 10, 2017 at 11:23:32AM +0100, Mark Rutland wrote:
>> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
>> > (+Mark, Grant)
>> >
>> > On 09/10/17 18:16, Chris Metcalf wrote:
>> > > The
On Tue, Oct 10, 2017 at 12:58 PM, Leif Lindholm
wrote:
>
> On Tue, Oct 10, 2017 at 11:23:32AM +0100, Mark Rutland wrote:
>> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
>> > (+Mark, Grant)
>> >
>> > On 09/10/17 18:16, Chris Metcalf wrote:
>> > > The Mellanox BlueField SoC
On Tue, Oct 10, 2017 at 11:23:32AM +0100, Mark Rutland wrote:
> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
> > (+Mark, Grant)
> >
> > On 09/10/17 18:16, Chris Metcalf wrote:
> > > The Mellanox BlueField SoC firmware supports a safe upgrade mode as
> > > part of the flow where
On Tue, Oct 10, 2017 at 11:23:32AM +0100, Mark Rutland wrote:
> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
> > (+Mark, Grant)
> >
> > On 09/10/17 18:16, Chris Metcalf wrote:
> > > The Mellanox BlueField SoC firmware supports a safe upgrade mode as
> > > part of the flow where
On 10 October 2017 at 11:23, Mark Rutland wrote:
> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
>> (+Mark, Grant)
>>
>> On 09/10/17 18:16, Chris Metcalf wrote:
>> > The Mellanox BlueField SoC firmware supports a safe upgrade mode as
>> > part of the flow
On 10 October 2017 at 11:23, Mark Rutland wrote:
> On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
>> (+Mark, Grant)
>>
>> On 09/10/17 18:16, Chris Metcalf wrote:
>> > The Mellanox BlueField SoC firmware supports a safe upgrade mode as
>> > part of the flow where users put new
On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
> (+Mark, Grant)
>
> On 09/10/17 18:16, Chris Metcalf wrote:
> > The Mellanox BlueField SoC firmware supports a safe upgrade mode as
> > part of the flow where users put new firmware on the secondary eMMC
> > boot partition (the one
On Tue, Oct 10, 2017 at 11:15:39AM +0100, Sudeep Holla wrote:
> (+Mark, Grant)
>
> On 09/10/17 18:16, Chris Metcalf wrote:
> > The Mellanox BlueField SoC firmware supports a safe upgrade mode as
> > part of the flow where users put new firmware on the secondary eMMC
> > boot partition (the one
(+Mark, Grant)
On 09/10/17 18:16, Chris Metcalf wrote:
> The Mellanox BlueField SoC firmware supports a safe upgrade mode as
> part of the flow where users put new firmware on the secondary eMMC
> boot partition (the one not currently in use), tell the eMMC to make
> the secondary boot partition
(+Mark, Grant)
On 09/10/17 18:16, Chris Metcalf wrote:
> The Mellanox BlueField SoC firmware supports a safe upgrade mode as
> part of the flow where users put new firmware on the secondary eMMC
> boot partition (the one not currently in use), tell the eMMC to make
> the secondary boot partition
The Mellanox BlueField SoC firmware supports a safe upgrade mode as
part of the flow where users put new firmware on the secondary eMMC
boot partition (the one not currently in use), tell the eMMC to make
the secondary boot partition primary, and reset. This driver is
used to request that the
The Mellanox BlueField SoC firmware supports a safe upgrade mode as
part of the flow where users put new firmware on the secondary eMMC
boot partition (the one not currently in use), tell the eMMC to make
the secondary boot partition primary, and reset. This driver is
used to request that the
14 matches
Mail list logo