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: <1255397413-4862-1-git-send-email-tabbott@ksplice.com>
Date:	Mon, 12 Oct 2009 21:30:06 -0400
From:	Tim Abbott <tabbott@...lice.com>
To:	Greg Ungerer <gerg@...pgear.com>
Cc:	linux-kernel@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
	Tim Abbott <tabbott@...lice.com>
Subject: [PATCH v3 0/7] m68knommu: Clean up linker script using new linker script macros.

On Mon, 12 Oct 2009, Greg Ungerer wrote:
> Tim Abbott wrote:
>> I don't any good ideas for what in patch is likely to be
>> responsible.  Would it be helpful to debug if I split this into ~5
>> very small patches so that we can find out what part of the patch
>> is responsible?
> Yes, that will make it quick and easy for me.

OK, below's a new patch series that is the same as the previous one
but in 7-patch format.

	-Tim Abbott

Tim Abbott (7):
  m68knommu: Don't hardcode the value of PAGE_SIZE in the linker
    script.
  m68knommu: Make THREAD_SIZE available to assembly files.
  m68knommu: Use INIT_TASK_DATA and CACHELINE_ALIGNED_DATA.
  m68knommu: Use more macros inside the .init section.
  m68knommu: Move __init_begin out of the .init section.
  m68knommu: Move __init_end out of the .init section.
  m68knommu: Split the .init section into INIT_TEXT_SECTION and
    INIT_DATA_SECTION.

 arch/m68k/include/asm/thread_info_no.h |    4 +-
 arch/m68knommu/kernel/vmlinux.lds.S    |   41 ++++++++-----------------------
 2 files changed, 13 insertions(+), 32 deletions(-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ