[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdk3EPurHLMf81VHowauRYZ4FZXxNg98hJvp8CLgu=SSPw@mail.gmail.com>
Date: Thu, 19 Dec 2019 09:06:37 -0800
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Kalle Valo <kvalo@...eaurora.org>
Cc: Nathan Chancellor <natechancellor@...il.com>,
Network Development <netdev@...r.kernel.org>,
linux-wireless@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
ath11k@...ts.infradead.org
Subject: Re: [PATCH] ath11k: Remove unnecessary enum scan_priority
On Thu, Dec 19, 2019 at 5:32 AM Kalle Valo <kvalo@...eaurora.org> wrote:
>
> Nick Desaulniers <ndesaulniers@...gle.com> writes:
>
> > On Wed, Dec 11, 2019 at 11:23 AM Nathan Chancellor
> > <natechancellor@...il.com> wrote:
> >> wmi_scan_priority and scan_priority have the same values but the wmi one
> >> has WMI prefixed to the names. Since that enum is already being used,
> >> get rid of scan_priority and switch its one use to wmi_scan_priority to
> >> fix this warning.
> >>
> > Also, I don't know if the more concisely named enum is preferable?
>
> I didn't get this comment.
Given two enums with the same values:
enum scan_priority
enum wmi_scan_priority
wouldn't you prefer to type wmi_ a few times less? Doesn't really
matter, but that was the point I was making.
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists