Hi Huacai,
On Wed, Jun 13, 2018 at 01:55:17PM +0800, Huacai Chen wrote:
> > Additionally you have "Resend" in the subject of this email, but I don't
> > see any previous submissions of this patch - given that commit
> > 7f56b58a92aaf2c ("locking/mcs: Use smp_cond_load_acquire() in MCS spin
> > loop") is very recent I doubt there were any. Please try to be factual,
> > and if you have 2 patches that are unrelated please send them separately
> > rather than as a series.
> I send another patch in this series because it is so simple and should
> be merged in the previous release, but it is ignored again and again.
> In practise, my
> single patch in linux-mips usually be ignored (even they are very
> simple and well described)....
> For example:
> https://patchwork.linux-mips.org/patch/17723/
> https://patchwork.linux-mips.org/patch/18587/
> https://patchwork.linux-mips.org/patch/19184/
>
> Some of them are promised by James to review, but still ignored until now.
Both James & Ralf have been busy with things outside of kernel
development recently, so I'm sure it's just the case that they've not
had as much time to spend on maintenance as would have been ideal. I
know that has been frustrating, but the reasons for that haven't always
been controllable & I feel confident saying that it was nobody's intent
to ignore you or your contributions.
Going forwards I'm now listed in MAINTAINERS & after v4.18-rc1 is
released I intend to start merging patches ready for v4.19. I've started
looking though pending patches but haven't gotten as far as the ones you
linked yet.
A couple of those look like they could be candidates for a fixes pull in
the 4.18 cycle so I'll try to take a closer look at those sooner.
I'm still getting up to speed & there is a backlog of patches to review,
but please be assured that if your patch is still listed as "New" or
"Under Review" in patchwork then I intend to look at it, and there's no
need to resend it.
Thanks,
Paul
