linux-kernel - Re: [PATCH v11 0/6] Driver for at91 usart in spi mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180823112349.GB28860@dell>
Date:   Thu, 23 Aug 2018 12:23:49 +0100
From:   Lee Jones <lee.jones@...aro.org>
To:     Radu Pirea <radu.pirea@...rochip.com>
Cc:     "broonie@...nel.org" <broonie@...nel.org>,
        Nicolas Ferre - M43238 <Nicolas.Ferre@...rochip.com>,
        "alexandre.belloni@...tlin.com" <alexandre.belloni@...tlin.com>,
        "richard.genoud@...il.com" <richard.genoud@...il.com>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "mark.rutland@....com" <mark.rutland@....com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>
Subject: Re: [PATCH v11 0/6] Driver for at91 usart in spi mode

On Wed, 22 Aug 2018, Radu Pirea wrote:
> I saw that the patches were not applied to your tree for this kernel
> version. After the discussion with Nicolas, I remember that you said that
> you will take the patches in your tree. I addressed Mark comments related to
> the last version of patches. Is there something that must be reworked in
> order to take the patches?

I don't remember back this far, so can't provide you with any good
reasons as to why the set wasn't applied.  There doesn't appear to be
anything wrong or wanting from the set, although it was submitted late
in the release cycle.

Just to let you and other readers know; since email is almost
exclusively used for submitting, reviewing and tracking patches, and
my setup (mbsync/mutt) can be a little temperamental at times, there
are instances, albeit rare ones when patches/sets fall by the
wayside.  In these instances, my suggestion is always for the
submitter to resubmit with a RESEND in order to regain attention to
the set.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog