linux-kernel - Re: [PATCH v2 1/3] dmaengine: ptdma: Initial driver for the AMD PassThru DMA engine

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]

Date:   Fri, 3 Jan 2020 16:52:56 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Gary R Hook <gary.hook@....com>
Cc:     Vinod Koul <vkoul@...nel.org>,
        Sanjay R Mehta <Sanju.Mehta@....com>,
        kbuild test robot <lkp@...el.com>, dan.j.williams@...el.com,
        Nehal-bakulchandra.Shah@....com, Shyam-sundar.S-k@....com,
        davem@...emloft.net, mchehab+samsung@...nel.org, robh@...nel.org,
        Jonathan.Cameron@...wei.com, linux-kernel@...r.kernel.org,
        dmaengine@...r.kernel.org
Subject: Re: [PATCH v2 1/3] dmaengine: ptdma: Initial driver for the AMD
 PassThru DMA engine

On Fri, Jan 03, 2020 at 09:12:18AM -0600, Gary R Hook wrote:
> On 1/3/20 12:26 AM, Vinod Koul wrote:
> > On 28-12-19, 07:56, kbuild test robot wrote:
> > > Hi Sanjay,
> > > 
> > > I love your patch! Perhaps something to improve:
> > 
> > Please fix the issues reported and also make sure the patches sent are
> > threaded, right now they are not and the series is all over my inbox :(
> > 
> 
> What does this mean? The patches showed up in my inbox as a set of 3,
> properly indexed, just like they should when sent with "git send-email".
> 
> We've not had any reports from other lists/maintainers of similar problems.
> So you'll understand how we might be a bit confused.
> 
> Would you please elaborate on the problem you are seeing?

There was no email threading of the patches, they all looked like
individual emails.  In other words, the "In-Reply-To:" value was not
set.

thanks,

greg k-h