From: Greg KH <greg@kroah.com>
To: claudius.heine.ext@siemens.com
Cc: stable@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Ley Foon Tan <lftan@altera.com>, Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v4.4 0/7] PCI: altera: survive warm reboot
Date: Thu, 10 Jan 2019 20:15:07 +0100 [thread overview]
Message-ID: <20190110191507.GE18221@kroah.com> (raw)
In-Reply-To: <20190107100056.12721-1-claudius.heine.ext@siemens.com>
On Mon, Jan 07, 2019 at 11:00:49AM +0100, claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> Hi,
>
> after a warm reboot, the altera pcie host interface is not correctly
> initialized in v4.4.
>
> These patches from v4.9 solved that issue.
I only received 4 patches from this series for some reason.
Can you resend them all again?
Or just provide the git commit ids, if no backporting is needed.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-10 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:00 [PATCH v4.4 0/7] PCI: altera: survive warm reboot claudius.heine.ext
2019-01-07 10:00 ` [PATCH v4.4 1/7] PCI: altera: Fix altera_pcie_link_is_up() claudius.heine.ext
2019-01-07 10:00 ` [PATCH v4.4 2/7] PCI: altera: Reorder read/write functions claudius.heine.ext
2019-01-07 10:00 ` [PATCH v4.4 3/7] PCI: altera: Check link status before retrain link claudius.heine.ext
2019-01-07 10:00 ` [PATCH v4.4 4/7] PCI: altera: Poll for link up status after retraining the link claudius.heine.ext
2019-01-07 10:00 ` [PATCH v4.4 5/7] PCI: altera: Poll for link training " claudius.heine.ext
2019-01-07 10:00 ` [PATCH v4.4 6/7] PCI: altera: Rework config accessors for use without a struct pci_bus claudius.heine.ext
2019-01-07 10:00 ` [PATCH v4.4 7/7] PCI: altera: Move retrain from fixup to altera_pcie_host_init() claudius.heine.ext
2019-01-10 19:15 ` Greg KH [this message]
2019-01-14 8:24 ` [PATCH v4.4 0/7] PCI: altera: survive warm reboot Claudius Heine
2019-01-14 17:40 ` Greg KH
2019-01-15 8:34 ` Claudius Heine
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=20190110191507.GE18221@kroah.com \
--to=greg@kroah.com \
--cc=bhelgaas@google.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=lftan@altera.com \
--cc=stable@vger.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).