Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <ff05bd36b338f4f914780176e9eba8138e1b254b.1536927765.git.christophe.leroy@c-s.fr>
 <20180916190610.vzqxwps7zqy2zc6o@holly.lan> <5f0e0241-b7ab-b5fa-de0e-01abdbc85770@linaro.org>
 <760ed3ff-43d9-75e5-b36c-aaa7871ffe50@c-s.fr> <877ej7urh3.fsf@concordia.ellerman.id.au>
 <7cf2d115-a58b-4585-37fc-7e58169a43a3@c-s.fr> <87zhw1srt4.fsf@concordia.ellerman.id.au>
 <ca845d92-674b-4ca2-3535-2621972bd13b@windriver.com>
In-Reply-To: <ca845d92-674b-4ca2-3535-2621972bd13b@windriver.com>
From:   Olof Johansson <olof@lixom.net>
Date:   Sat, 10 Nov 2018 13:42:04 -0800
Message-ID: <CAOesGMiv3Qh52GhqmTXJ4LDNEfsoOp2BO_C2H_T3wsY2A6k5zQ@mail.gmail.com>
Subject: Re: [PATCH] kdb: use correct pointer when 'btc' calls 'btt'
To:     Jason Wessel <jason.wessel@windriver.com>
Cc:     Michael Ellerman <mpe@ellerman.id.au>, christophe.leroy@c-s.fr,
        Daniel Thompson <daniel.thompson@linaro.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
        kgdb-bugreport@lists.sourceforge.net,
        stable <stable@vger.kernel.org>, me@tobin.cc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Jason,

On Mon, Oct 1, 2018 at 12:52 PM Jason Wessel <jason.wessel@windriver.com> w=
rote:
>
> On 09/28/2018 07:57 AM, Michael Ellerman wrote:
> > Christophe LEROY <christophe.leroy@c-s.fr> writes:
> >> Le 27/09/2018 =C3=A0 13:09, Michael Ellerman a =C3=A9crit :
> >>> Christophe LEROY <christophe.leroy@c-s.fr> writes:
> >>>> Le 26/09/2018 =C3=A0 13:11, Daniel Thompson a =C3=A9crit :
> >>>>
> >>>> The Fixes: and now your Reviewed-by: appear automatically in patchwo=
rk
> >>>> (https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=3D65=
715),
> >>>> so I believe they'll be automatically included when Jason or someone
> >>>> else takes the patch, no ?
> >>>
> >>> patchwork won't add the Fixes tag from the reply, it needs to be in t=
he
> >>> original mail.
> >>>
> >>> See:
> >>>     https://github.com/getpatchwork/patchwork/issues/151
> >>>
> >>
> >> Ok, so it accounts it and adds a '1' in the F column in the patches
> >> list, but won't take it into account.
> >
> > Yes. The logic that populates the columns is separate from the logic
> > that scrapes the tags, which is a bug :)
> >
> >> Then I'll send a v2 with revised commit text.
> >
>
>
> No need.  https://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.gi=
t/commit/?h=3Dkgdb-next
>
> Since it is a regression fix, we'll try and get it merged as soon as we c=
an.

Looks like this didn't make it in yet, even with a merge window inbetween? =
:(

I know first-hand that time to do upstream work can sometimes be hard
to find. I also know that Daniel has shown interest in helping out
here, and is listed as a maintainer. May I suggest that he starts a
tree to collect patches and submit pull requests for a while, until
you find more time for it?

Having a tag-team maintainer setup like we have had for arm-soc has
been very useful especially when one of us get too busy for a while,
etc.


-Olof