From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
arcml <linux-snps-arc@lists.infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ARC updates for 5.5-rc6
Date: Mon, 6 Jan 2020 18:09:39 +0000 [thread overview]
Message-ID: <9907df0c-6996-1a6b-0cf1-0dbfcb8ea414@synopsys.com> (raw)
Hi Linus,
Happy New Year. Please pull ARC fixed for 5.5-rc6.
Thx,
-Vineet
----------------->
The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git/ tags/arc-5.5-rc6
for you to fetch changes up to 7ecc6c1d5c8dbc713c647512a5267ca0eafe3e1c:
ARC: pt_regs: remove hardcoded registers offset (2019-12-28 13:05:08 -0800)
----------------------------------------------------------------
ARC fixes for v5.5-rc6
- Kconfig warning, stale define, duplicate asm-offset entry ...
----------------------------------------------------------------
Eugeniy Paltsev (2):
ARC: asm-offsets: remove duplicate entry
ARC: pt_regs: remove hardcoded registers offset
Mike Rapoport (1):
ARC: mm: drop stale define of __ARCH_USE_5LEVEL_HACK
Randy Dunlap (1):
arc: eznps: fix allmodconfig kconfig warning
arch/arc/include/asm/entry-arcv2.h | 8 ++++----
arch/arc/include/asm/hugepage.h | 1 -
arch/arc/kernel/asm-offsets.c | 10 +++++++++-
arch/arc/plat-eznps/Kconfig | 2 +-
4 files changed, 14 insertions(+), 7 deletions(-)
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next reply other threads:[~2020-01-06 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 18:09 Vineet Gupta [this message]
2020-01-06 21:05 ` [GIT PULL] ARC updates for 5.5-rc6 pr-tracker-bot
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=9907df0c-6996-1a6b-0cf1-0dbfcb8ea414@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=rppt@linux.vnet.ibm.com \
--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).