linux-kernel - Re: [patch] propagate name change to comments in kernel source

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: <1354756634.9720.203.camel@tisifone>
Date:	Wed, 05 Dec 2012 20:17:14 -0500
From:	Nadia Yvette Chambers <nyc@...omorphy.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jiri Kosina <jkosina@...e.cz>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch] propagate name change to comments in kernel source

On Thu, 2012-12-06 at 12:01 +1100, Stephen Rothwell wrote:
> OK, that may be a problem.  Does this patch apply to Linus' tree
> currently?  I guess not.  So, either you need to split it up and send it
> to the various maintainers (most if it can probably go through the trivial
> tree (cc'd)).  Or wait until after v3.8-rc1 and fix it so it applies to
> Linus' tree and send it to him.
> Or Andrew (cc'd) may be able to take it (as his tree is based on
> linux-next currently).
> (I have attached the patch for Jiri's and Andrew's benefit)

It applies with offsets to Linus' current git, actually. I can provide a
diff applying with no offsets, but suspect it's unnecessary. The
affected comment blocks don't seem to have experienced much turnover
recently, if ever.

-- nyc


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