From: Bjorn Helgaas <helgaas@kernel.org>
To: "Олег Мороз" <oleg.moroz@mcc.vniiem.ru>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Joerg Roedel <jroedel@suse.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, Sunjin Yang <fan4326@gmail.com>,
linux-acpi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yinghai@kernel.org>,
Jiang Liu <jiang.liu@linux.intel.com>
Subject: Re: [PATCH v2 0/3] PCI: Revert "Implement pcibios_alloc_irq() and pcibios_free_irq()"
Date: Thu, 25 Feb 2016 08:53:10 -0600 [thread overview]
Message-ID: <20160225145310.GA23155@localhost> (raw)
In-Reply-To: <56CDF6E0.2060005@mcc.vniiem.ru>
On Wed, Feb 24, 2016 at 09:30:56PM +0300, Олег Мороз wrote:
> I've checked next next-20160218 tag and confirm that it works.
Thanks a lot for testing this! I added your tested-by to the commit.
I apologize again for the inconvenience of this. Thank you very much
for your effort in reporting it and helping track it down.
Bjorn
> 18.02.2016 19:03, Bjorn Helgaas пишет:
> >On Thu, Feb 18, 2016 at 08:13:41AM +0300, Мороз Олег wrote:
> >>On 17.02.2016 21:36, Bjorn Helgaas wrote:
> >>>These are clean reverts of 991de2e59090 ("PCI, x86: Implement
> >>>pcibios_alloc_irq() and pcibios_free_irq()") and related changes.
> >>>
> >>>We have two reports of drivers broken in v4.3 by Jiang's change,
> >>>991de2e59090 ("PCI, x86: Implement pcibios_alloc_irq() and
> >>>pcibios_free_irq()").
> >>>
> >>>It would be best to fix the problem instead of reverting 991de2e59090, but
> >>>I don't have time to do that myself, and we haven't heard from Jiang, so
> >>>the only choice I have is to revert the commit.
> >>>
> >>>Note that reverting will likely break IOAPIC hotplug.
> >>>
> >>>Олег and Sunjin, can you please test this and see whether it fixes your
> >>>drivers? This patch is based on v4.5-rc1.
> >>>
> >>>I intend to merge these for v4.5 unless I hear objections.
> >>>
> >>>They're on my for-linus branch, so they should appear in linux-next
> >>>tomorrow.
> >>>
> >>>Changes from the v1 posting:
> >>> - Explicitly revert related patches instead of resolving conflicts
> >>> manually
> >>>---
> >>>
> >>>Bjorn Helgaas (3):
> >>> Revert "x86/PCI: Don't alloc pcibios-irq when MSI is enabled"
> >>> Revert "PCI: Add helpers to manage pci_dev->irq and pci_dev->irq_managed"
> >>> Revert "PCI, x86: Implement pcibios_alloc_irq() and pcibios_free_irq()"
> >>>
> >>>
> >>> arch/x86/include/asm/pci_x86.h | 2 ++
> >>> arch/x86/pci/common.c | 26 ++++++++++----------------
> >>> arch/x86/pci/intel_mid_pci.c | 9 +++------
> >>> arch/x86/pci/irq.c | 23 +++++++++++++++++++----
> >>> drivers/acpi/pci_irq.c | 17 +++++++++++++----
> >>> include/linux/pci.h | 17 -----------------
> >>> 6 files changed, 47 insertions(+), 47 deletions(-)
> >>As i undestand this patch will appear in kernel git repo tomorrow? I
> >>don't need to apply in manyally to v4.5-rc1?
> >These are included in the next-20160218 tag in the linux-next git repo (not
> >Linus' repo) at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> >
> >You browse this at:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/
> >
> >If you'd rather, you can also apply the patches yourself to v4.5-rc1.
> >
> >Bjorn
>
prev parent reply other threads:[~2016-02-25 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 18:36 [PATCH v2 0/3] PCI: Revert "Implement pcibios_alloc_irq() and pcibios_free_irq()" Bjorn Helgaas
2016-02-17 18:37 ` [PATCH v2 1/3] Revert "x86/PCI: Don't alloc pcibios-irq when MSI is enabled" Bjorn Helgaas
2016-02-17 18:37 ` [PATCH v2 2/3] Revert "PCI: Add helpers to manage pci_dev->irq and pci_dev->irq_managed" Bjorn Helgaas
2016-02-17 18:37 ` [PATCH v2 3/3] Revert "PCI, x86: Implement pcibios_alloc_irq() and pcibios_free_irq()" Bjorn Helgaas
2016-02-17 19:47 ` [PATCH v2 0/3] PCI: Revert "Implement " Rafael J. Wysocki
2016-02-18 5:13 ` Мороз Олег
2016-02-18 16:03 ` Bjorn Helgaas
2016-02-24 18:30 ` Олег Мороз
2016-02-25 14:53 ` Bjorn Helgaas [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=20160225145310.GA23155@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=fan4326@gmail.com \
--cc=jiang.liu@linux.intel.com \
--cc=jroedel@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=oleg.moroz@mcc.vniiem.ru \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).