[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181210203036.GA18150@altlinux.org>
Date: Mon, 10 Dec 2018 23:30:36 +0300
From: "Dmitry V. Levin" <ldv@...linux.org>
To: Max Filippov <jcmvbkbc@...il.com>
Cc: Oleg Nesterov <oleg@...hat.com>,
Andrew Lutomirski <luto@...nel.org>,
Elvira Khabirova <lineprinter@...linux.org>,
Eugene Syromyatnikov <esyr@...hat.com>,
Chris Zankel <chris@...kel.net>,
Paul Moore <paul@...l-moore.com>,
Eric Paris <eparis@...hat.com>, linux-xtensa@...ux-xtensa.org,
linux-audit@...hat.com, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 19/25] xtensa: define syscall_get_* functions
On Mon, Dec 10, 2018 at 11:24:02PM +0300, Dmitry V. Levin wrote:
> On Mon, Dec 10, 2018 at 12:14:37PM -0800, Max Filippov wrote:
> > On Mon, Dec 10, 2018 at 4:53 AM Dmitry V. Levin <ldv@...linux.org> wrote:
> > > On Sun, Dec 09, 2018 at 09:02:50PM -0800, Max Filippov wrote:
> > > > How should we synchronize our changes?
> > >
> > > No problem, I can revert to the previous edition of this patch
> > > that just adds syscall_get_arch.
> > > Alternatively, you can just take that couple of patches (v5 18/25
> > > and v2 15/15) into your tree.
> >
> > Sure I can do the second. Will it work for v2 16/15 that changes
> > syscall_get_arch adding an argument to it?
>
> No, I'm afraid it won't work for v2 16/15 (aka v5 22/25), which means
> I'd have to keep them in the series.
You can surely take them into your tree, but I'll have to keep them
in the series because of that change of syscall_get_arch signature.
Sorry for confusion.
--
ldv
Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)
Powered by blists - more mailing lists