Hi Jason,
On Mon, Oct 1, 2018 at 12:52 PM Jason Wessel jason.wessel@windriver.com wrote:
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.
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=k...
Since it is a regression fix, we'll try and get it merged as soon as we can.
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