On 7/21/2020 3:19 PM, Jiri Pirko wrote:
Tue, Jul 21, 2020 at 11:51:21AM CEST, vasundhara-v.vo...@broadcom.com wrote:
On Wed, Jul 1, 2020 at 3:17 PM Jiri Pirko wrote:
Wed, Jul 01, 2020 at 11:25:50AM CEST, vasundhara-v.vo...@broadcom.com wrote:
On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrot
Tue, Jul 21, 2020 at 11:51:21AM CEST, vasundhara-v.vo...@broadcom.com wrote:
>On Wed, Jul 1, 2020 at 3:17 PM Jiri Pirko wrote:
>>
>> Wed, Jul 01, 2020 at 11:25:50AM CEST, vasundhara-v.vo...@broadcom.com wrote:
>> >On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrote:
>> >>
>> >> Tue, Jun 30, 2020 at
On Wed, Jul 1, 2020 at 3:17 PM Jiri Pirko wrote:
>
> Wed, Jul 01, 2020 at 11:25:50AM CEST, vasundhara-v.vo...@broadcom.com wrote:
> >On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrote:
> >>
> >> Tue, Jun 30, 2020 at 05:15:18PM CEST, vasundhara-v.vo...@broadcom.com
> >> wrote:
> >> >On Tue, Jun 30,
On 7/10/2020 1:39 PM, Jakub Kicinski wrote:
> On Fri, 10 Jul 2020 11:16:51 -0700 Jacob Keller wrote:
>>> We already have notion of "a component" in "devlink dev flash". I think
>>> that the reset component name should be in-sync with the flash.
>>
>> Right. We should re-use the component names from
On Fri, 10 Jul 2020 11:16:51 -0700 Jacob Keller wrote:
> > We already have notion of "a component" in "devlink dev flash". I think
> > that the reset component name should be in-sync with the flash.
>
> Right. We should re-use the component names from devlink dev info here
> (just as we do in devl
On 7/1/2020 2:47 AM, Jiri Pirko wrote:
> Wed, Jul 01, 2020 at 11:25:50AM CEST, vasundhara-v.vo...@broadcom.com wrote:
>> On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrote:
>>>
>>> Tue, Jun 30, 2020 at 05:15:18PM CEST, vasundhara-v.vo...@broadcom.com wrote:
On Tue, Jun 30, 2020 at 6:23 PM Ji
Wed, Jul 01, 2020 at 01:59:14PM CEST, vasundhara-v.vo...@broadcom.com wrote:
>On Wed, Jul 1, 2020 at 3:17 PM Jiri Pirko wrote:
>>
>> Wed, Jul 01, 2020 at 11:25:50AM CEST, vasundhara-v.vo...@broadcom.com wrote:
>> >On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrote:
>> >>
>> >> Tue, Jun 30, 2020 at
On Wed, Jul 1, 2020 at 3:17 PM Jiri Pirko wrote:
>
> Wed, Jul 01, 2020 at 11:25:50AM CEST, vasundhara-v.vo...@broadcom.com wrote:
> >On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrote:
> >>
> >> Tue, Jun 30, 2020 at 05:15:18PM CEST, vasundhara-v.vo...@broadcom.com
> >> wrote:
> >> >On Tue, Jun 30,
Wed, Jul 01, 2020 at 11:25:50AM CEST, vasundhara-v.vo...@broadcom.com wrote:
>On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrote:
>>
>> Tue, Jun 30, 2020 at 05:15:18PM CEST, vasundhara-v.vo...@broadcom.com wrote:
>> >On Tue, Jun 30, 2020 at 6:23 PM Jiri Pirko wrote:
>> >>
>> >> Tue, Jun 30, 2020 at
On Wed, Jul 1, 2020 at 11:21 AM Jiri Pirko wrote:
>
> Tue, Jun 30, 2020 at 05:15:18PM CEST, vasundhara-v.vo...@broadcom.com wrote:
> >On Tue, Jun 30, 2020 at 6:23 PM Jiri Pirko wrote:
> >>
> >> Tue, Jun 30, 2020 at 01:34:06PM CEST, vasundhara-v.vo...@broadcom.com
> >> wrote:
> >> >Advanced NICs
Tue, Jun 30, 2020 at 05:15:18PM CEST, vasundhara-v.vo...@broadcom.com wrote:
>On Tue, Jun 30, 2020 at 6:23 PM Jiri Pirko wrote:
>>
>> Tue, Jun 30, 2020 at 01:34:06PM CEST, vasundhara-v.vo...@broadcom.com wrote:
>> >Advanced NICs support live reset of some of the hardware
>> >components, that reset
On Tue, Jun 30, 2020 at 6:23 PM Jiri Pirko wrote:
>
> Tue, Jun 30, 2020 at 01:34:06PM CEST, vasundhara-v.vo...@broadcom.com wrote:
> >Advanced NICs support live reset of some of the hardware
> >components, that resets the device immediately with all the
> >host drivers loaded.
> >
> >Add devlink r
Tue, Jun 30, 2020 at 01:34:06PM CEST, vasundhara-v.vo...@broadcom.com wrote:
>Advanced NICs support live reset of some of the hardware
>components, that resets the device immediately with all the
>host drivers loaded.
>
>Add devlink reset subcommand to support live and deferred modes
>of reset. It
13 matches
Mail list logo