mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org,
	Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: [PULL 0/4] Xtensa fixes for v4.20
Date: Thu,  1 Nov 2018 14:03:45 -0700	[thread overview]
Message-ID: <20181101210345.9076-1-jcmvbkbc@gmail.com> (raw)

Hi Linus,

please pull the following batch of fixes and cleanups for the Xtensa
architecture:
The following changes since commit 35a7f35ad1b150ddf59a41dcac7b2fa32982be0e:

  Linux 4.19-rc8 (2018-10-15 07:20:24 +0200)

are available in the git repository at:

  git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20181101

for you to fetch changes up to 960b82c383d38fea4439e4182b5be4352a6048e2:

  xtensa: clean up xtensa-specific property sections (2018-10-30 01:28:56 -0700)

----------------------------------------------------------------
Xtensa fixes and cleanups for v4.20:

- use ZONE_NORMAL instead of ZONE_DMA;
- fix Image.elf build error caused by assignment of incorrect address
  to the .note.Linux section;
- clean up debug and property sections in the vmlinux.lds.S.

----------------------------------------------------------------
Christoph Hellwig (1):
      xtensa: remove ZONE_DMA

Max Filippov (3):
      xtensa: add NOTES section to the linker script
      xtensa: use DWARF_DEBUG in the vmlinux.lds.S
      xtensa: clean up xtensa-specific property sections

 arch/xtensa/Kconfig              |  3 ---
 arch/xtensa/boot/Makefile        |  2 +-
 arch/xtensa/kernel/vmlinux.lds.S | 36 +++++-------------------------------
 arch/xtensa/mm/init.c            |  2 +-
 4 files changed, 7 insertions(+), 36 deletions(-)

Thanks.
-- Max

             reply	other threads:[~2018-11-01 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 21:03 Max Filippov [this message]
2018-11-01 21:35 ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181101210345.9076-1-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=chris@zankel.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®