linux-kernel - Re: [PATCH v3 1/4] kbuild: Don't define ALIGN and ENTRY when preprocessing linker scripts.

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]

Date:	Sun, 20 Sep 2009 23:43:12 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Tim Abbott <tabbott@...lice.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/4] kbuild: Don't define ALIGN and ENTRY when
	preprocessing linker scripts.

On Sun, Sep 20, 2009 at 05:24:50PM -0400, Tim Abbott wrote:
> On Sun, 20 Sep 2009, Sam Ravnborg wrote:
> 
> > The reason for __XXX___ for ASSEMBLY and KERNEL is the fact
> > that these are used in user space headers.
> > 
> > I would suggest to use: LINKER_SCRIPT
> 
> OK.  I'm happy with calling it LINKER_SCRIPT.
> 
> > This will conflict (in a trivial way) with stuff I have
> > pending for this merge window.
> 
> Is that pending stuff available in a public git repository somewhere?  If 
> so, I could send you a version on top of those pending changes.  
> (Alternatively, if you're planning to take this patch, I'd be fine with 
> your resolving the merge conflict, updating the name, and putting it in 
> with your stuff.  Whatever's easier for you).

git.kernel.org - kbuild-next.git

I rebased earlier today and have pushed it out right now.
Please rebase and send me a new set.
I will take these four as they touch a lot architectures.

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