[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200427145527.GA71654@furthur.local>
Date: Mon, 27 Apr 2020 16:55:27 +0200
From: Lubomir Rintel <lkundrak@...sk>
To: Lee Jones <lee.jones@...aro.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] mfd: Add ENE KB3930 Embedded Controller driver
On Mon, Apr 27, 2020 at 07:48:24AM +0100, Lee Jones wrote:
> On Sat, 25 Apr 2020, Lubomir Rintel wrote:
>
> > Hi,
> >
> > please take a look at the following patch set and consider applying it
> > to the MFD tree. It a new driver with DT binding documentation changes,
> > utilized by the LED driver submitted here:
> >
> > https://lore.kernel.org/lkml/20200424220240.106055-1-lkundrak@v3.sk/
>
> What is this? The subject suggests this is a cover-letter for a
> patch-set, but the patches are not attached to it. If this is the
> case, please ensure that you send it --threaded using
>
> `git send-email`
>
> If it's just a random plea to go look at some set posted onto a
> mailing list without me on Cc, then no. Please send the set again,
> properly, with me listed as a recipient.
It indeed is a cover letter for a patch set, it had the patches chained to
it, with you as a recipient, and it was sent with git send-email. If you
haven't recevied them then I have no idea why. I do apologize in case it's
my fault.
Perhaps your spam filter dropped them? In that case I'm wondering what
could bump the spam score for the patches, but not the cover letter.
In any case, the archive received them:
https://lore.kernel.org/lkml/20200424221123.106527-1-lkundrak@v3.sk/
I wouldn't mind resending the messages, but I'd prefer to understand
what happened to them first.
Lubo
Powered by blists - more mailing lists