From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
imunsie@au1.ibm.com, mikey@neuling.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: cxl: Fix informational message
Date: Tue, 13 Sep 2016 22:16:34 +1000 (AEST) [thread overview]
Message-ID: <3sYNvQ4v8Hz9t0m@ozlabs.org> (raw)
In-Reply-To: <1473676663-11057-1-git-send-email-fbarrat@linux.vnet.ibm.com>
On Mon, 2016-12-09 at 10:37:43 UTC, Frederic Barrat wrote:
> When set_sl_ops() is called, the adapter data structure is not fully
> initialized yet. Therefore the device name is not showing up in the
> trace. Fix is simply to get the device name from the pci_dev
> structure.
>
> Fixes: 6d382616ac22 ("cxl: Abstract the differences between the PSL and XSL")
> Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b135077b83f01549c2a0685b16
cheers
prev parent reply other threads:[~2016-09-13 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 10:37 [PATCH] cxl: Fix informational message Frederic Barrat
2016-09-13 3:49 ` Andrew Donnellan
2016-09-13 12:16 ` Michael Ellerman [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=3sYNvQ4v8Hz9t0m@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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).