From: Greg KH <greg@kroah.com>
To: Nhan Nguyen <nhan.nguyen.yb@renesas.com>
Cc: yasushi.onishi.xc@renesas.com, binh.nguyen.uw@rvc.renesas.com,
thongsyho <thong.ho.px@rvc.renesas.com>,
stable@vger.kernel.org, Julian Scheel <julian@jusst.de>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 4.4.y] ASoC: simple-card: Fix misleading error message
Date: Mon, 5 Feb 2018 09:53:48 -0800 [thread overview]
Message-ID: <20180205175348.GA20308@kroah.com> (raw)
In-Reply-To: <20180205031135.7420-1-nhan.nguyen.yb@renesas.com>
On Mon, Feb 05, 2018 at 10:11:35AM +0700, Nhan Nguyen wrote:
> From: thongsyho <thong.ho.px@rvc.renesas.com>
That author is not the author of:
> commit 7ac45d1635a4cd2e99a4b11903d4a2815ca1b27b upstream.
^ that commit :(
> In case cpu could not be found the error message would always refer to
> /codec/ not being found in DT. Fix this by catching the cpu node not found
> case explicitly.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Julian Scheel <julian@jusst.de>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: thongsyho <thong.ho.px@rvc.renesas.com>
As you are forwarding these patches on to me, I need your signed-off-by
as well on these patches.
Also, I have no idea what order these should all be applied in. Please
fix the above issues, and resend this series, and the series for the 4.9
kernel tree, as a numbered patch series so I have a hint as to what
order to apply them.
thanks,
greg k-h
next prev parent reply other threads:[~2018-02-05 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 3:11 [PATCH 4.4.y] ASoC: simple-card: Fix misleading error message Nhan Nguyen
2018-02-05 17:53 ` Greg KH [this message]
2018-02-06 6:30 ` Nhan Ngoc. Nguyen
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=20180205175348.GA20308@kroah.com \
--to=greg@kroah.com \
--cc=binh.nguyen.uw@rvc.renesas.com \
--cc=broonie@kernel.org \
--cc=julian@jusst.de \
--cc=nhan.nguyen.yb@renesas.com \
--cc=stable@vger.kernel.org \
--cc=thong.ho.px@rvc.renesas.com \
--cc=yasushi.onishi.xc@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.