From: Jason Wessel <jason.wessel@windriver.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Christophe LEROY <christophe.leroy@c-s.fr>,
Daniel Thompson <daniel.thompson@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
<kgdb-bugreport@lists.sourceforge.net>, <stable@vger.kernel.org>,
<me@tobin.cc>
Subject: Re: [PATCH] kdb: use correct pointer when 'btc' calls 'btt'
Date: Mon, 1 Oct 2018 14:52:11 -0500 [thread overview]
Message-ID: <ca845d92-674b-4ca2-3535-2621972bd13b@windriver.com> (raw)
In-Reply-To: <87zhw1srt4.fsf@concordia.ellerman.id.au>
On 09/28/2018 07:57 AM, Michael Ellerman wrote:
> Christophe LEROY <christophe.leroy@c-s.fr> writes:
>> Le 27/09/2018 à 13:09, Michael Ellerman a écrit :
>>> Christophe LEROY <christophe.leroy@c-s.fr> writes:
>>>> Le 26/09/2018 à 13:11, Daniel Thompson a écrit :
>>>>
>>>> The Fixes: and now your Reviewed-by: appear automatically in patchwork
>>>> (https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=65715),
>>>> 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 the
>>> 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.git/commit/?h=kgdb-next
Since it is a regression fix, we'll try and get it merged as soon as we can.
Cheers,
Jason.
next prev parent reply other threads:[~2018-10-01 19:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 12:35 [PATCH] kdb: use correct pointer when 'btc' calls 'btt' Christophe Leroy
2018-09-16 19:06 ` Daniel Thompson
2018-09-16 22:18 ` Tobin C. Harding
2018-09-26 11:11 ` Daniel Thompson
2018-09-26 11:19 ` Christophe LEROY
2018-09-27 11:09 ` Michael Ellerman
2018-09-27 11:30 ` Christophe LEROY
2018-09-28 12:57 ` Michael Ellerman
2018-10-01 19:52 ` Jason Wessel [this message]
2018-11-10 21:42 ` Olof Johansson
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=ca845d92-674b-4ca2-3535-2621972bd13b@windriver.com \
--to=jason.wessel@windriver.com \
--cc=christophe.leroy@c-s.fr \
--cc=daniel.thompson@linaro.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=me@tobin.cc \
--cc=mpe@ellerman.id.au \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).