From: palmer@sifive.com (Palmer Dabbelt)
To: linux-riscv@lists.infradead.org
Subject: [GIT PULL] A Single RISC-V Update for 4.19-rc6
Date: Mon, 24 Sep 2018 13:45:31 -0700 (PDT) [thread overview]
Message-ID: <mhng-e3afd7a0-8f32-43a2-98bc-ef162868bede@palmer-si-x1c4> (raw)
The following changes since commit 6bf4ca7fbc85d80446ac01c0d1d77db4d91a6d84:
Linux 4.19-rc5 (2018-09-23 19:15:18 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git tags/riscv-for-linus-4.19-rc6
for you to fetch changes up to 57a489786de9ec37d6e25ef1305dc337047f0236:
RISC-V: include linux/ftrace.h in asm-prototypes.h (2018-09-24 13:12:27 -0700)
----------------------------------------------------------------
A Single RISC-V Update for 4.19-rc6
The Debian guys have been pushing on our port and found some unversioned
symbols leaking into modules. This PR contains a single fix for that
issue.
----------------------------------------------------------------
James Cowgill (1):
RISC-V: include linux/ftrace.h in asm-prototypes.h
arch/riscv/include/asm/asm-prototypes.h | 7 +++++++
1 file changed, 7 insertions(+)
create mode 100644 arch/riscv/include/asm/asm-prototypes.h
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@sifive.com>
To: linux-riscv@lists.infradead.org
Subject: [GIT PULL] A Single RISC-V Update for 4.19-rc6
Date: Mon, 24 Sep 2018 13:45:31 -0700 (PDT) [thread overview]
Message-ID: <mhng-e3afd7a0-8f32-43a2-98bc-ef162868bede@palmer-si-x1c4> (raw)
Message-ID: <20180924204531.gcO3qnr1iyvIwg53P0YTVwxDSy2V0M5tW0MlFkJJB3A@z> (raw)
The following changes since commit 6bf4ca7fbc85d80446ac01c0d1d77db4d91a6d84:
Linux 4.19-rc5 (2018-09-23 19:15:18 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git tags/riscv-for-linus-4.19-rc6
for you to fetch changes up to 57a489786de9ec37d6e25ef1305dc337047f0236:
RISC-V: include linux/ftrace.h in asm-prototypes.h (2018-09-24 13:12:27 -0700)
----------------------------------------------------------------
A Single RISC-V Update for 4.19-rc6
The Debian guys have been pushing on our port and found some unversioned
symbols leaking into modules. This PR contains a single fix for that
issue.
----------------------------------------------------------------
James Cowgill (1):
RISC-V: include linux/ftrace.h in asm-prototypes.h
arch/riscv/include/asm/asm-prototypes.h | 7 +++++++
1 file changed, 7 insertions(+)
create mode 100644 arch/riscv/include/asm/asm-prototypes.h
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-09-24 20:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 20:45 Palmer Dabbelt [this message]
2018-09-24 20:45 ` [GIT PULL] A Single RISC-V Update for 4.19-rc6 Palmer Dabbelt
2018-09-25 16:15 ` Christoph Hellwig
2018-09-25 16:15 ` Christoph Hellwig
2018-09-25 16:26 ` Palmer Dabbelt
2018-09-25 16:26 ` Palmer Dabbelt
2018-09-25 17:32 ` Christoph Hellwig
2018-09-25 17:32 ` Christoph Hellwig
2018-09-25 17:57 ` Palmer Dabbelt
2018-09-25 17:57 ` Palmer Dabbelt
2018-09-27 18:51 Palmer Dabbelt
2018-09-27 18:51 ` Palmer Dabbelt
2018-09-27 18:51 ` Palmer Dabbelt
2018-09-28 16:54 ` Greg KH
2018-09-28 16:54 ` Greg KH
2018-09-28 16:54 ` Greg KH
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=mhng-e3afd7a0-8f32-43a2-98bc-ef162868bede@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=linux-riscv@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.