On Wed, Jun 22, 2022 at 06:20:04AM +0200, Philipp Hortmann wrote:
> On 6/7/22 19:23, Greg KH wrote:
> > And again, please help review code, otherwise you are just asking others
> > to do work for you, which if you think about it, could be construed as a
> > bit selfish, and I don't think you mean
On 6/7/22 19:23, Greg KH wrote:
And again, please help review code, otherwise you are just asking others
to do work for you, which if you think about it, could be construed as a
bit selfish, and I don't think you mean it to be.
Hi Greg,
this applies to me. I promise to improve. But this topic
On Tue, Jun 07, 2022 at 12:19:03PM -0500, Ian Pilcher wrote:
> On 11/19/21 01:08, Greg KH wrote:
> > As the merge window is now over, please just resend the patches.
> > Remember maintainers can not add anything to their trees usually for the
> > week before, and during the 2 weeks of, the merge
On 11/19/21 01:08, Greg KH wrote:
As the merge window is now over, please just resend the patches.
Remember maintainers can not add anything to their trees usually for the
week before, and during the 2 weeks of, the merge window, so that might
account for the delay here.
Also, just resend
On Thu, Nov 18, 2021 at 01:55:41PM -0600, Ian Pilcher wrote:
> I am looking for advice on how to proceed when kernel patch reviewers
> stop responding to patches. I've been working on a patch series for
> several months - sending 3 "RFC" and 8 non-RFC versions, receiving
> feedback, and
I am looking for advice on how to proceed when kernel patch reviewers
stop responding to patches. I've been working on a patch series for
several months - sending 3 "RFC" and 8 non-RFC versions, receiving
feedback, and implementing all of the changes that have been requested.
I sent the last
