public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] h8300 update
Date: Thu, 21 Jan 2016 13:49:19 +0900	[thread overview]
Message-ID: <87egdbsfjk.wl-ysato@users.sourceforge.jp> (raw)

Hello Linus,
Could you pull this changes.

The following changes since commit 2c487121e3c4f87e82cff493872675bde52e47fc:

  Merge tag 'leds-for-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds (2016-01-11 20:40:48 -0800)

are available in the git repository at:

  git://git.osdn.jp/gitroot/uclinux-h8/linux.git tags/for-4.5

for you to fetch changes up to 2f1b0077a9604eda130ffb0313c2f1e9db424269:

  h8300: System call entry enable interrupt. (2016-01-20 23:28:01 +0900)

----------------------------------------------------------------
Add KGDB support.
zImage fix.
various cleanup

----------------------------------------------------------------
Geert Uytterhoeven (1):
      clk: h8300: Remove "sh73a0-" part from compatible value

Guenter Roeck (1):
      irqchip: renesas-h8s: Replace ctrl_outw/ctrl_inw with writew/readw

Yoshinori Sato (8):
      h8300: zImage alignment fix
      h8300: zImage alignment fix
      h8300: Add LZO compression
      h8300: signal stack fix
      h8300: Add KGDB support.
      h8300: Restraint of warning.
      h8300: show_stack cleanup
      h8300: System call entry enable interrupt.

 .../bindings/clock/renesas,h8300-div-clock.txt     |   2 +-
 arch/h8300/Kconfig                                 |   3 +
 arch/h8300/boot/compressed/Makefile                |  11 +-
 arch/h8300/boot/compressed/misc.c                  |   6 +
 arch/h8300/boot/compressed/vmlinux.lds             |   4 +-
 arch/h8300/include/asm/io.h                        |   8 +-
 arch/h8300/include/asm/kgdb.h                      |  45 +++++++
 arch/h8300/include/asm/traps.h                     |   2 +-
 arch/h8300/kernel/Makefile                         |   2 +
 arch/h8300/kernel/entry.S                          |  19 +++
 arch/h8300/kernel/kgdb.c                           | 135 +++++++++++++++++++++
 arch/h8300/kernel/signal.c                         |   8 +-
 arch/h8300/kernel/traps.c                          |  20 ++-
 drivers/irqchip/irq-renesas-h8s.c                  |  10 +-
 14 files changed, 244 insertions(+), 31 deletions(-)
 create mode 100644 arch/h8300/include/asm/kgdb.h
 create mode 100644 arch/h8300/kernel/kgdb.c

-- 
Yoshinori Sato
<ysato@users.sourceforge.jp>

             reply	other threads:[~2016-01-21  4:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  4:49 Yoshinori Sato [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-24 16:50 [GIT PULL] h8300 update Yoshinori Sato
2015-11-12  4:51 Yoshinori Sato
2010-01-11  5:29 [git pull] " Yoshinori Sato
2010-01-11  5:29 Yoshinori Sato
2010-01-11  5:29 Yoshinori Sato
2010-01-11  5:29 Yoshinori Sato
2010-01-11  5:29 Yoshinori Sato
2010-01-11  5:28 Yoshinori Sato

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=87egdbsfjk.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=linux-kernel@vger.kernel.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