linux-kernel - Re: [PATCH ] x86 : Fix compilation warning on paravirt-spinlocks.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b9df5fa10812092228qe618ablaca61adc05f947ab@mail.gmail.com>
Date:	Wed, 10 Dec 2008 12:28:14 +0600
From:	"Rakib Mullick" <rakib.mullick@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Linux-kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [PATCH ] x86 : Fix compilation warning on paravirt-spinlocks.c

On 12/8/08, Ingo Molnar <mingo@...e.hu> wrote:
>
>  * Rakib Mullick <rakib.mullick@...il.com> wrote:
>
> no - this just works around the compiler warning.
>
>  Look at the real fix below i did some time ago. If you are into fixing
>  warnings you should try tip/master, that has a ton of warning fixes
>  already:
>
>   http://people.redhat.com/mingo/tip.git/README
>
>         Ingo
Thanks, Ingo for explanation. In 'default_spin_lock_flags' function ,
the 2nd argument unsigned long flags isn't used in the function. Is it
necessary to keep it ?

Thanks,
Rakib.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/