linux-kernel - Re: [PATCH] CHROMIUM: acerhdf: fix bug when running on Qemu

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] [day] [month] [year] [list]

Message-ID: <20100506204952.GA13101@google.com>
Date:	Thu, 6 May 2010 13:49:52 -0700
From:	Mandeep Singh Baines <msb@...omium.org>
To:	Peter Feuerer <pfe@...e.net>
Cc:	Rahul Chaturvedi <rkc@...omium.org>, linux-kernel@...r.kernel.org,
	msb@...omium.org
Subject: Re: [PATCH] CHROMIUM: acerhdf: fix bug when running on Qemu

Peter Feuerer (pfe@...e.net) wrote:
> Rahul Chaturvedi writes:
>
>> BTW, the CHROMIUM in the subject is just used for internal bookeeping
>> for patches not yet accepted upstream.
>
> What does it mean? Should I take care about getting it upstream?
>

You can drop it. We use it for internal bookkeeping in the chromium
git tree.

http://chromiumos-git/?p=kernel.git

Its useful to us when we rebase our kernel to a new 2.6.x.
We use it to record which tree the patch came from: did it come from
upstream, did we write, did we pull it from a maintainer tree.

> --peter;
--
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/