powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a004-20201006
x86_64 randconfig-a002-20201006
x86_64 randconfig-a001-20201006
x86_64
My name is Reem Hashimy, the Emirates Minister of State and Managing Director
of the United Arab Emirates (Dubai) World Expo 2020 Committee which has been
postponed to October 2021 to March 2022 because of the Covid-19 pandemic.
I am writing to you to manage the funds I received as financial gr
counter_atomic* is introduced to be used when a variable is used as
a simple counter and doesn't guard object lifetimes. This clearly
differentiates atomic_t usages that guard object lifetimes.
counter_atomic* variables will wrap around to 0 when it overflows and
should not be used to guard resour
This patch series is a result of discussion at the refcount_t BOF
the Linux Plumbers Conference. In this discussion, we identified
a need for looking closely and investigating atomic_t usages in
the kernel when it is used strictly as a counter without it
controlling object lifetimes and state chang
This patch fixes check of a result of 'power_up()' function call in
function 'gc0310_s_power()' to do "error handling" instead of "success
handling" as Dan Carpenter noted in his comment on the previous patch.
Lines 'return gc0310_init(sd)' and 'return ret' are swapped, and direct
value of 'ret' is
On Tue, 2020-10-06 at 21:04 +0300, Dan Carpenter wrote:
> Code should generally do "error handling" instead of "success handling".
Maybe something to add to coding-style
(in '6} Functions' maybe?)...
> That way the success path is always indented one tab and the error path
> is indented two tabs.
On Tue, Oct 06, 2020 at 10:17:21AM +0200, Leonid Kushnir wrote:
> This patch fixes the checkpatch.pl warning :
>
> WARNING: else is not generally useful after a break or return
>
> Expressions under 'else' branch in function 'gc0310_s_power' are
> executed whenever the exppression in 'if' is Fals
On 9/28/20 5:13 PM, Kees Cook wrote:
On Mon, Sep 28, 2020 at 04:41:47PM -0600, Shuah Khan wrote:
On 9/26/20 10:29 AM, Kees Cook wrote:
On Fri, Sep 25, 2020 at 05:47:14PM -0600, Shuah Khan wrote:
7. Verified that the test module compiles in kunit env. and test
module can be loaded
After a list_for_each_entry() loop, the list iterator is always non-NULL
so these conditions don't work. If the "waiter" is not found then this
results in an out of bounds access.
I have fixed it by introducing a new "found" variable. In one case, I
used an else statement for readability.
Fixes
This patch fixes the checkpatch.pl warning :
WARNING: else is not generally useful after a break or return
Expressions under 'else' branch in function 'gc0310_s_power' are
executed whenever the exppression in 'if' is False. Otherwise, return
from function occurs. Therefore, there is no need in 'e
10 matches
Mail list logo
