From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Vaibhav Jain <vaibhav@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org,
Cc: , Vaibhav Jain <vaibhav@linux.ibm.com>, stable@vger.kernel.org
Subject: Re: [RESEND PATCH v3] cxl: Wrap iterations over afu slices inside 'afu_list_lock'
Date: Wed, 30 Jan 2019 14:46:44 +0000 [thread overview]
Message-ID: <20190130144645.0218E218A3@mail.kernel.org> (raw)
In-Reply-To: <20190129110618.13481-1-vaibhav@linux.ibm.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: .
The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96, v4.9.153, v4.4.172, v3.18.133.
v4.20.5: Build OK!
v4.19.18: Build OK!
v4.14.96: Build OK!
v4.9.153: Failed to apply! Possible dependencies:
bb81733de28c ("cxl: Fix error handling in _cxl_pci_associate_default_context()")
v4.4.172: Failed to apply! Possible dependencies:
14baf4d9c739 ("cxl: Add guest-specific code")
2b04cf310ba8 ("cxl: Rename some bare-metal specific functions")
5be587b11101 ("cxl: Introduce implementation-specific API")
73d55c3b59f7 ("cxl: IRQ allocation for guests")
8633186209e3 ("cxl: Move common code away from bare-metal-specific files")
cbffa3a5146a ("cxl: Separate bare-metal fields in adapter and AFU data structures")
d56d301b5174 ("cxl: Move bare-metal specific code to specialized files")
ea2d1f95efd7 ("cxl: Isolate a few bare-metal-specific calls")
v3.18.133: Failed to apply! Possible dependencies:
0520336afe5d ("cxl: Export file ops for use by API")
0b3f9c757cab ("cxl: Drop commands if the PCI channel is not in normal state")
14baf4d9c739 ("cxl: Add guest-specific code")
27d4dc7116ee ("cxl: Implement an ioctl to fetch afu card-id, offset-id and mode")
3d6b040e7338 ("cxl: sparse: Make declarations static")
406e12ec0b64 ("cxl: Cleanup Makefile")
456295e284be ("cxl: Fix leaking interrupts if attach process fails")
588b34be20bc ("cxl: Convert MMIO read/write macros to inline functions")
5be587b11101 ("cxl: Introduce implementation-specific API")
62fa19d4b4fd ("cxl: Add ability to reset the card")
6428832a7bfa ("cxl: Add cookie parameter to afu_release_irqs()")
6f7f0b3df6d4 ("cxl: Add AFU virtual PHB and kernel API")
73d55c3b59f7 ("cxl: IRQ allocation for guests")
7bb5d91a4dda ("cxl: Rework context lifetimes")
80c394fab896 ("cxl: Add explicit precision specifiers")
80fa93fce37d ("cxl: Name interrupts in /proc/interrupt")
8dde152ea348 ("cxl: fix leak of IRQ names in cxl_free_afu_irqs()")
95bc11bcd142 ("cxl: Add image control to sysfs")
9bcf28cdb28e ("cxl: Add tracepoints")
b087e6190ddc ("cxl: Export optional AFU configuration record in sysfs")
b12994fbfe93 ("cxl: cxl_afu_reset() -> __cxl_afu_reset()")
bc78b05bb412 ("cxl: Return error to PSL if IRQ demultiplexing fails & print clearer warning")
c358d84b4e57 ("cxl: Split afu_register_irqs() function")
cbffa3a5146a ("cxl: Separate bare-metal fields in adapter and AFU data structures")
de369538436a ("cxl: use more common format specifier")
e36f6fe1f7aa ("cxl: Export AFU error buffer via sysfs")
ea2d1f95efd7 ("cxl: Isolate a few bare-metal-specific calls")
eda3693c842e ("cxl: Rework detach context functions")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-01-30 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 11:06 [RESEND PATCH v3] cxl: Wrap iterations over afu slices inside 'afu_list_lock' Vaibhav Jain
2019-01-30 12:41 ` Michael Ellerman
2019-01-30 13:25 ` Vaibhav Jain
2019-01-30 14:46 ` Sasha Levin [this message]
2019-02-08 13:02 ` [RESEND, " Michael Ellerman
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=20190130144645.0218E218A3@mail.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vaibhav@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).