[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOHTAphUCUnY03yaZJCAXG2eODFP3EFfGo+FUMV9cjcmmzABqw@mail.gmail.com>
Date: Wed, 6 Dec 2017 17:34:08 -0500
From: Alexander Aring <aring@...atatu.com>
To: David Miller <davem@...emloft.net>
Cc: Jamal Hadi Salim <jhs@...atatu.com>,
Cong Wang <xiyou.wangcong@...il.com>,
Jiří Pírko <jiri@...nulli.us>,
netdev@...r.kernel.org, kernel@...atatu.com,
David Ahern <dsahern@...il.com>
Subject: Re: [PATCH net-next 0/6] net: sched: sch: introduce extack support
Hi,
On Wed, Dec 6, 2017 at 3:40 PM, David Miller <davem@...emloft.net> wrote:
> From: Alexander Aring <aring@...atatu.com>
> Date: Wed, 6 Dec 2017 11:08:39 -0500
>
>> this patch series basically add support for extack in common qdisc handling.
>> Additional it adds extack pointer to common qdisc callback handling this
>> offers per qdisc implementation to setting the extack message for each
>> failure over netlink.
>>
>> The extack message will be set deeper in qdisc functions but going not
>> deeper as net core api. For qdisc module callback handling, the extack
>> will not be set. This will be part of per qdisc extack handling.
>>
>> I also want to prepare patches to handle extack per qdisc module...
>> so there will come a lot of more patches, just cut them down to make
>> it reviewable.
>>
>> There are some above 80-chars width warnings, which I ignore because
>> it looks more ugly otherwise.
>>
>> This patch-series based on patches by David Ahren which gave me some
>> hints how to deal with extack support.
>>
>> Cc: David Ahern <dsahern@...il.com>
>
> Only add the plumbing when you have actual extack messages you are
> adding as an example use case.
>
I did not understand. I have a lot of patches which make use of these
changes. Do you want me to submit me these in one shot (patch-series)?
I was hoping to making it in smaller patch-series for easier review.
- Alex
Powered by blists - more mailing lists