From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Helge Deller <deller@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
John David Anglin <dave.anglin@bell.net>
Subject: Re: [GIT PULL] parisc fixes for kernel v4.19
Date: Tue, 2 Oct 2018 14:16:45 -0700 [thread overview]
Message-ID: <20181002211645.GA6454@kroah.com> (raw)
In-Reply-To: <20181002210213.GA17826@ls3530.fritz.box>
On Tue, Oct 02, 2018 at 11:02:13PM +0200, Helge Deller wrote:
> Hi Greg,
>
> please pull a last set of fixes for the parisc architecture for kernel 4.19 from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.19-3
>
> The major change is for parisc64 to use a 64-bit suseconds_t type to
> match what glibc expects for 64-bit userspace. It's an ABI change, but
> since we don't have a 64-bit userspace on parisc yet, it won't introduce
> a breakage.
Isn't it a bit "late" in the release cycle for such a change? Why not
do this on the -rc1 release?
> Other than that we simply drop unused code and outdated gcc version
> checks.
Why are those needed now?
thanks,
greg k-h
next prev parent reply other threads:[~2018-10-02 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 21:02 [GIT PULL] parisc fixes for kernel v4.19 Helge Deller
2018-10-02 21:16 ` Greg Kroah-Hartman [this message]
2018-10-02 21:46 ` Helge Deller
2018-10-02 22:24 ` Greg Kroah-Hartman
2018-10-03 14:47 ` Helge Deller
2018-10-03 18:16 ` Greg Kroah-Hartman
2018-10-03 19:49 ` Arnd Bergmann
2018-10-03 23:02 ` gregkh
2018-10-04 8:41 ` Helge Deller
2018-10-04 13:34 ` Arnd Bergmann
2018-10-04 14:30 ` Helge Deller
2018-10-04 14:38 ` Helge Deller
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=20181002211645.GA6454@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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 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.