[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VetWKfWWm1gwpd_KjhbXXV-cb1F=DvPVXPKy6v7x6hsBw@mail.gmail.com>
Date: Tue, 2 May 2017 23:27:02 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Christian König <deathsimple@...afone.de>
Cc: helgaas@...nel.org,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
dri-devel@...ts.freedesktop.org,
Platform Driver <platform-driver-x86@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/4] PCI: add functionality for resizing resources v3
On Tue, May 2, 2017 at 6:51 PM, Christian König <deathsimple@...afone.de> wrote:
> Am 26.04.2017 um 19:00 schrieb Andy Shevchenko:
>> On Tue, Apr 25, 2017 at 4:19 PM, Christian König
>> <deathsimple@...afone.de> wrote:
>>> +int pci_reassign_bridge_resources(struct pci_dev *bridge, unsigned long
>>> type)
>>> +{
>>> + const unsigned long type_mask = IORESOURCE_IO | IORESOURCE_MEM |
>>> + IORESOURCE_PREFETCH | IORESOURCE_MEM_64;
>>> +
>>
>> Redundant.
>
>
> Redundant, but also a reminder to myself that I wanted to ask something
> about that.
Missed context I suppose. Usually I comment in one word something
obvious, i.e. redundant empty line.
Sorry for missing my point.
> This type_mask is used already three times in this file, shouldn't we add a
> define for that?
Yes, that's wxactly what I commented somewhere (in one of the rest cases).
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists