From: Benjamin GAIGNARD <benjamin.gaignard@st.com>
To: Wei Yongjun <weiyongjun1@huawei.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH -next] hwspinlock: fix return value check in stm32_hwspinlock_probe()
Date: Thu, 03 Jan 2019 10:06:07 +0000 [thread overview]
Message-ID: <16205f0c-3514-731c-e948-38695e3a525d@st.com> (raw)
In-Reply-To: <1546498950-105456-1-git-send-email-weiyongjun1@huawei.com>
DQpPbiAxLzMvMTkgODowMiBBTSwgV2VpIFlvbmdqdW4gd3JvdGU6DQo+IEluIGNhc2Ugb2YgZXJy
b3IsIHRoZSBmdW5jdGlvbiBkZXZtX2lvcmVtYXBfcmVzb3VyY2UoKSByZXR1cm5zIEVSUl9QVFIo
KQ0KPiBhbmQgbmV2ZXIgcmV0dXJucyBOVUxMLiBUaGUgTlVMTCB0ZXN0IGluIHRoZSByZXR1cm4g
dmFsdWUgY2hlY2sgc2hvdWxkDQo+IGJlIHJlcGxhY2VkIHdpdGggSVNfRVJSKCkuDQo+DQo+IEZp
eGVzOiBmMjRmY2ZmMWQyNjcgKCJod3NwaW5sb2NrOiBhZGQgU1RNMzIgaHdzcGlubG9jayBkZXZp
Y2UiKQ0KPiBTaWduZWQtb2ZmLWJ5OiBXZWkgWW9uZ2p1biA8d2VpeW9uZ2p1bjFAaHVhd2VpLmNv
bT4NCkFja2VkLWJ5OiBCZW5qYW1pbiBHYWlnbmFyZCA8YmVuamFtaW4uZ2FpZ25hcmRAZ21haWwu
Y29tPg0KPiAtLS0NCj4gICBkcml2ZXJzL2h3c3BpbmxvY2svc3RtMzJfaHdzcGlubG9jay5jIHwg
NCArKy0tDQo+ICAgMSBmaWxlIGNoYW5nZWQsIDIgaW5zZXJ0aW9ucygrKSwgMiBkZWxldGlvbnMo
LSkNCj4NCj4gZGlmZiAtLWdpdCBhL2RyaXZlcnMvaHdzcGlubG9jay9zdG0zMl9od3NwaW5sb2Nr
LmMgYi9kcml2ZXJzL2h3c3BpbmxvY2svc3RtMzJfaHdzcGlubG9jay5jDQo+IGluZGV4IDM0YThl
MDAuLjQ0MTgzOTIgMTAwNjQ0DQo+IC0tLSBhL2RyaXZlcnMvaHdzcGlubG9jay9zdG0zMl9od3Nw
aW5sb2NrLmMNCj4gKysrIGIvZHJpdmVycy9od3NwaW5sb2NrL3N0bTMyX2h3c3BpbmxvY2suYw0K
PiBAQCAtNTcsOCArNTcsOCBAQCBzdGF0aWMgaW50IHN0bTMyX2h3c3BpbmxvY2tfcHJvYmUoc3Ry
dWN0IHBsYXRmb3JtX2RldmljZSAqcGRldikNCj4gICANCj4gICAJcmVzID0gcGxhdGZvcm1fZ2V0
X3Jlc291cmNlKHBkZXYsIElPUkVTT1VSQ0VfTUVNLCAwKTsNCj4gICAJaW9fYmFzZSA9IGRldm1f
aW9yZW1hcF9yZXNvdXJjZSgmcGRldi0+ZGV2LCByZXMpOw0KPiAtCWlmICghaW9fYmFzZSkNCj4g
LQkJcmV0dXJuIC1FTk9NRU07DQo+ICsJaWYgKElTX0VSUihpb19iYXNlKSkNCj4gKwkJcmV0dXJu
IFBUUl9FUlIoaW9fYmFzZSk7DQo+ICAgDQo+ICAgCWFycmF5X3NpemUgPSBTVE0zMl9NVVRFWF9O
VU1fTE9DS1MgKiBzaXplb2Yoc3RydWN0IGh3c3BpbmxvY2spOw0KPiAgIAlodyA9IGRldm1fa3ph
bGxvYygmcGRldi0+ZGV2LCBzaXplb2YoKmh3KSArIGFycmF5X3NpemUsIEdGUF9LRVJORUwpOw0K
Pg0KPg0KPg=
next prev parent reply other threads:[~2019-01-03 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 6:56 [PATCH -next] hwspinlock: fix return value check in stm32_hwspinlock_probe() Wei Yongjun
2019-01-03 10:06 ` Benjamin GAIGNARD [this message]
2019-01-03 20:07 ` Bjorn Andersson
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=16205f0c-3514-731c-e948-38695e3a525d@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=ohad@wizery.com \
--cc=weiyongjun1@huawei.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