From: Tony Lindgren <tony@atomide.com>
To: cgel.zte@gmail.com
Cc: aaro.koskinen@iki.fi, jmkrzyszt@gmail.com, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jinpeng Cui <cui.jinpeng2@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] ARM: omap1: remove redundant variables err
Date: Mon, 27 Mar 2023 10:11:21 +0300 [thread overview]
Message-ID: <20230327071121.GR7501@atomide.com> (raw)
In-Reply-To: <20220830142136.299373-1-cui.jinpeng2@zte.com.cn>
* cgel.zte@gmail.com <cgel.zte@gmail.com> [220830 17:14]:
> From: Jinpeng Cui <cui.jinpeng2@zte.com.cn>
>
> Rturn value directly from platform_device_register()
> instead of getting value from redundant variable err.
Sorry looks like this is still pending, applying into
omap-for-v6.4/omap1 thanks.
Tony
prev parent reply other threads:[~2023-03-27 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 14:21 [PATCH linux-next] ARM: omap1: remove redundant variables err cgel.zte
2022-09-05 20:46 ` Janusz Krzysztofik
2023-03-27 7:11 ` Tony Lindgren [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=20230327071121.GR7501@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=cgel.zte@gmail.com \
--cc=cui.jinpeng2@zte.com.cn \
--cc=jmkrzyszt@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=zealci@zte.com.cn \
/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