[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpURjzhNniuV0pObucCmWCS5whGp3q6a0NyC_euagx-Dhw@mail.gmail.com>
Date: Wed, 6 Dec 2017 11:10:41 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Alexander Aring <aring@...atatu.com>
Cc: David Miller <davem@...emloft.net>,
Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Pirko <jiri@...nulli.us>,
Linux Kernel Network Developers <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
On Wed, Dec 6, 2017 at 8:08 AM, Alexander Aring <aring@...atatu.com> wrote:
> Hi,
>
> 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>
Acked-by: Cong Wang <xiyou.wangcong@...il.com>
Powered by blists - more mailing lists