[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1557cd7b-ccbf-6202-83ea-20923700d260@deltatee.com>
Date: Mon, 17 Jun 2019 10:55:15 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Bjorn Helgaas <helgaas@...nel.org>,
Nicholas Johnson <nicholas.johnson-opensource@...look.com.au>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>,
"corbet@....net" <corbet@....net>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [PATCH v6 0/4] PCI: Patch series to support Thunderbolt without
any BIOS support
On 2019-06-15 1:56 p.m., Bjorn Helgaas wrote:
> [+cc Ben, Logan]
>
> Ben, Logan, since you're looking at the resource code, maybe you'd be
> interested in this as well?
>
> On Wed, May 22, 2019 at 02:30:30PM +0000, Nicholas Johnson wrote:
>> Rebase patches to apply cleanly to 5.2-rc1 source. Remove patch for
>> comment style cleanup as this has already been applied.
>
> Thanks for rebasing these.
>
> They do apply cleanly, but they seem to be base64-encoded MIME
> attachments, and I don't know how to make mutt extract them easily. I
> had to save each patch attachment individually, apply it, insert the
> commit log manually, etc.
>
> Is there any chance you could send the next series as plain-text
> patches? That would be a lot easier for me.
I'd happily look at the patches but I can't find them. Sounds like they
were sent as attachments and it doesn't seem like the mailing list
archives keep those.
Logan
Powered by blists - more mailing lists