Hi,
Please pull for h8300 fix.
The following changes since commit 00c569b567c7f1f0da6162868fd02a9f29411805:
Merge tag 'locks-v4.21-1' of git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux (2018-12-27 17:12:30 -0800)
are available in the git repository at:
git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git tags/for-4.21
for you to fetch changes up to 21c7acc439b55d0569d7c2fc2eea5194b3910406:
h8300: pci: Remove local declaration of pcibios_penalize_isa_irq (2018-12-29 00:21:10 +0900)
----------------------------------------------------------------
h8300 build problem fix.
----------------------------------------------------------------
Guenter Roeck (1):
h8300: pci: Remove local declaration of pcibios_penalize_isa_irq
arch/h8300/include/asm/Kbuild | 1 +
arch/h8300/include/asm/pci.h | 18 ------------------
2 files changed, 1 insertion(+), 18 deletions(-)
delete mode 100644 arch/h8300/include/asm/pci.h
On Sat, Jan 5, 2019 at 1:34 AM Yoshinori Sato
<[email protected]> wrote:
>
> git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git tags/for-4.21
New signing key?
That's ok, but please sign it with your old one unless there's some
major reason you can't (ie "oops, I've lost the old one").
And yes, I see that the new key is nice and much stronger, but it
would still be nice to have the signature chain to your old one.
Linus
The pull request you sent on Sat, 05 Jan 2019 18:34:34 +0900:
> git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git tags/for-4.21
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/670b321f4150bfc8a2261f4db3fcdab21738506b
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
On Sun, 06 Jan 2019 04:40:55 +0900,
Linus Torvalds wrote:
>
> On Sat, Jan 5, 2019 at 1:34 AM Yoshinori Sato
> <[email protected]> wrote:
> >
> > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git tags/for-4.21
>
> New signing key?
Yes. My previous key was made more than 10 years ago, and it is not strong enough.
> That's ok, but please sign it with your old one unless there's some
> major reason you can't (ie "oops, I've lost the old one").
>
> And yes, I see that the new key is nice and much stronger, but it
> would still be nice to have the signature chain to your old one.
I intended to do so, but I will check it.
Thanks.
> Linus
--
Yosinori Sato