The pull request you sent on Fri, 1 Mar 2019 14:50:01 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
> tags/m68k-for-v5.1-tag1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/45f5532a2f65afeda9e8a02bf1aca15c2b4c9be8
Thank you!
--
On Tue, Mar 05, 2019 at 07:11:38PM +0100, Borislav Petkov wrote:
> I guess you could Cc arch maintainers with the a.out-core.h removal
> patch to see if anyone screams.
And they're like two for which we need confirmation:
$ git ls-files | grep a.out-core.h
arch/alpha/include/asm/a.out-core.h
On Tue, Mar 5, 2019 at 10:55 AM Finn Thain wrote:
> That leaves bvme6000, hp300, mvme147 and mvme16x. Those have not been
> tested. Here are some options for those platforms:
>
> 1) Apply the patches untested (gaining new clocksources and some API
> modernization for m68k, while fixing old bugs
On Tue, 5 Mar 2019, Geert Uytterhoeven wrote:
> On Tue, Mar 5, 2019 at 7:13 AM Finn Thain wrote:
> > On Sat, 1 Dec 2018, Finn Thain wrote:
> > > This series removes "select ARCH_USES_GETTIMEOFFSET" from arch/m68k
> > > and converts users of arch_gettimeoffset to the clocksource API.
> > >
On Mär 05 2019, Finn Thain wrote:
> interesting that the kernel's strlen implementation in
> include/linux/string.h can't achieve this.
This implementation is only available if ARCH_HAS_FORTIFY_SOURCE.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5
Hi Finn,
On Tue, Mar 5, 2019 at 9:58 AM Finn Thain wrote:
> On Tue, 5 Mar 2019, Geert Uytterhoeven wrote:
> > On Tue, Mar 5, 2019 at 3:58 AM Finn Thain
> > wrote:
> > > On Tue, 5 Mar 2019, Finn Thain wrote:
> > > > Looks bogus to me.
> > > >
> > > > If you change memcpy to __builtin_memcpy,
On Tue, 5 Mar 2019, Geert Uytterhoeven wrote:
> On Tue, Mar 5, 2019 at 3:58 AM Finn Thain wrote:
> > On Tue, 5 Mar 2019, Finn Thain wrote:
> > > Looks bogus to me.
> > >
> > > If you change memcpy to __builtin_memcpy, then we avoid the macro and the
> > > warning changes to,
> > >
> > >
