From: Hayes Wang <hayeswang@realtek.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: nic_swsd <nic_swsd@realtek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"pmalani@chromium.org" <pmalani@chromium.org>,
"grundler@chromium.org" <grundler@chromium.org>,
"'Linux Samsung SOC'" <linux-samsung-soc@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: RE: [PATCH net-next] r8152: support request_firmware for RTL8153
Date: Wed, 23 Oct 2019 11:52:45 +0000 [thread overview]
Message-ID: <0835B3720019904CB8F7AA43166CEEB2F18ED47C@RTITMBSVM03.realtek.com.tw> (raw)
In-Reply-To: <c20abd08-5f22-2cc8-15fa-956d06b5b8af@samsung.com>
Marek Szyprowski [mailto:m.szyprowski@samsung.com]
> Sent: Wednesday, October 23, 2019 6:23 PM
[...]
> >> This patch (which landed in linux-next last days) causes a following
> >> kernel oops on the ARM 32bit Exynos5422 SoC based Odroid XU4 board:
> > Please try the following patch.
>
> Yes, this fixes the issue. I've applied those changes manually on top of
> Linux next-20191022, due to some differences in the context. When you
> prepare a final patch, feel free to add:
>
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Fixes: 9370f2d05a2a ("r8152: support request_firmware for RTL8153")
> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
Thanks
Best Regards,
Hayes
prev parent reply other threads:[~2019-10-23 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 3:02 [PATCH net-next] r8152: support request_firmware for RTL8153 Hayes Wang
2019-10-16 18:31 ` David Miller
[not found] ` <CGME20191023091648eucas1p12dcc4e9041169e3c7ae43f4ea525dd7f@eucas1p1.samsung.com>
2019-10-23 9:16 ` Marek Szyprowski
2019-10-23 9:48 ` Hayes Wang
2019-10-23 10:22 ` Marek Szyprowski
2019-10-23 11:52 ` Hayes Wang [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=0835B3720019904CB8F7AA43166CEEB2F18ED47C@RTITMBSVM03.realtek.com.tw \
--to=hayeswang@realtek.com \
--cc=grundler@chromium.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pmalani@chromium.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).