From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Jason Cooper <jason@lakedaemon.net>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: mvebu: Remove redundant code
Date: Thu, 02 Jan 2014 11:52:23 +0100 [thread overview]
Message-ID: <52C544E7.4000501@free-electrons.com> (raw)
In-Reply-To: <20140102114638.47457689@skate>
On 02/01/2014 11:46, Thomas Petazzoni wrote:
> Dear Gregory CLEMENT,
>
> On Thu, 2 Jan 2014 11:41:36 +0100, Gregory CLEMENT wrote:
>> In the commit b42285f66f871a989, Sebastian moved clock enable before
>> register access, but during the merge of the commit
>> 9f352f0e6c0fa2dc608812df "PCI: mvebu: Dynamically detect if the PEX
>> link is up to enable hot plug", the moved part was added back.
>>
>> This patch fixes this by removing the redundant code.
>>
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> ---
>> drivers/pci/host/pci-mvebu.c | 8 --------
>> 1 file changed, 8 deletions(-)
>
> This has already been fixed by
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/pci/host/pci-mvebu.c?id=84f47190d6be1cb99cd4a680e1018080d93800a8.
>
I didn't find it because I only looked for in my emails and I
wrongly assumed that the LAKML were in CC.
> Thanks!
>
> Thomas
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2014-01-02 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 10:41 [PATCH] PCI: mvebu: Remove redundant code Gregory CLEMENT
2014-01-02 10:46 ` Thomas Petazzoni
2014-01-02 10:52 ` Gregory CLEMENT [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52C544E7.4000501@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=bhelgaas@google.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox