[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75Vd5RHc+CzxR+V5ixgKy5BpmD6Tx3bYG-hsYpAHJdYDgbw@mail.gmail.com>
Date: Mon, 18 Jun 2018 23:46:06 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH v3] bitfield: fix *_encode_bits()
On Mon, Jun 18, 2018 at 11:42 PM, Johannes Berg
<johannes@...solutions.net> wrote:
> On Mon, 2018-06-18 at 23:40 +0300, Andy Shevchenko wrote:
>
>> The idea is to print what was the input, expected output and actual result.
>> Then you would see what exactly is broken.
>
> Yeah, I guess we could. I did some of that work.
>
>> I dunno how much we may take away from this certain test case, though
>> it would be better for my opinion.
>
> TBH though, I'm not sure I want to do this (right now at least). I don't
> think we gain anything from it, it's so basic ... so to me it's just
> pointless extra code.
I'm not insisting I'm trying to specify rationale behind it.
We may add this later at some point.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists