linux-kernel - Re: [PATCH] Arch: x86: process: Fix a compilation warning.

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: <20110530130032.a4ec9757.rdunlap@xenotime.net>
Date:	Mon, 30 May 2011 13:00:32 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Rohit Yadav <rohityadav89@...il.com>
Cc:	Borislav Petkov <bp@...64.org>, Valdis.Kletnieks@...edu,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Arch: x86: process: Fix a compilation warning.

On Tue, 31 May 2011 01:22:54 +0530 Rohit Yadav wrote:

> > Yep, all valid points. Another one would be to search whether this got
> > already fixed before wasting effort:
> >
> > http://git.kernel.org/tip/598e887d8b01655780c81cc86a9e7820ed091580
> 
> What is the best way to search if something got fixed? There are
> plenty of repositories at git.kernel.org
> I'm using this one:
> http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

There are > 100 git trees, so just pick a few, like acpi, tip, arm, etc.,
and check them (I wouldn't expect anyone to check _all_ of them).

Or you could check mailing list archives: see here:
http://marc.info/?l=linux-kernel&m=130675351609350&w=2

It would be good IMO if -tip had a commits mailing list like
stable and -mm and mainline do.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/