On Fri, Jan 13, 2017 at 04:35:54PM +0100, Jack Wang wrote: > > > On 13.01.2017 16:01, Leon Romanovsky wrote: > > On Fri, Jan 13, 2017 at 02:12:19PM +0100, Jack Wang wrote: > >> Hi Doug, hi Jason and others, > >> > >> As Doug already merged the first 4 patches to his tree, so I rebased this patch also > >> on his latest for-4.11 branch (commit 102c5ce082), minor tweak on commit message. > >> I also configured my thunderbirds to keep the patch format as expected :), so here we go! > > > > Hi Jack, > > I don't know what did you configure, but git send-email is a preferred > > way to send linux kernel patches. > > > > Your attached patches are appearing wrongly (wrong subject and mbox garbage) in > > the patchworks https://patchwork.kernel.org/patch/9515651/ > > > > Thanks > > > Hi Leon, > > Thanks, I understand I changed subject in the patch because I notice Doug is using such naming. You changed the name of the patch which is fine, but you used the old thread and it was registered under that name in the system. Take a look on the subject of your patch: "[PATCH] RDMA/core: create struct ib_port_cache" and the name of in the system: "[PATCHv2,1/1] IB/core: create struct ib_port_cache" https://patchwork.kernel.org/patch/9515651/ > But I don't follow "mbox garbage", what do you mean here? Your patches contain all the wording at the beginning. Please download yours https://patchwork.kernel.org/patch/9515651/mbox/ and compare with the one in proper format https://patchwork.kernel.org/patch/9514391/mbox/ > > About git send-email, I used to successfully sent patch with the tool, but somehow it's now always get reject > by gmail. According to the email headers, gmail and git send-email works fine for the most participants here. > > I'm not familiar with patchwork, will reply to same thread with proper subject fix the problem or I have to do it in a new thread? No, please fix the setup before and submit it properly. Thanks. > > Thanks, > Jack
Attachment:
signature.asc
Description: PGP signature
