linux-kernel.vger.kernel.org archive mirror
 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/3] xtensa fixes for v4.19
Date: Fri, 14 Sep 2018 11:45:48 -0700	[thread overview]
Message-ID: <20180914184548.19187-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 57361846b52bc686112da6ca5368d11210796804:

  Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)

are available in the git repository at:

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

for you to fetch changes up to 4a7f50f78c221aac7253ea7059e1986eb622b0e5:

  xtensa: enable SG chaining in Kconfig (2018-09-11 22:12:59 -0700)

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

- don't allocate memory in platform_setup as the memory allocator is not
  initialized at that point yet;
- remove unnecessary ifeq KBUILD_SRC from arch/xtensa/Makefile;
- enable SG chaining in arch/xtensa/Kconfig.

----------------------------------------------------------------
Masahiro Yamada (1):
      xtensa: remove unnecessary KBUILD_SRC ifeq conditional

Max Filippov (2):
      xtensa: ISS: don't allocate memory in platform_setup
      xtensa: enable SG chaining in Kconfig

 arch/xtensa/Kconfig               |  1 +
 arch/xtensa/Makefile              |  4 ----
 arch/xtensa/platforms/iss/setup.c | 25 +++++++++++++++----------
 3 files changed, 16 insertions(+), 14 deletions(-)

Thanks.
-- Max

                 reply	other threads:[~2018-09-14 18:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180914184548.19187-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;
as well as URLs for NNTP newsgroup(s).