From: Tony Lindgren <tony@atomide.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: linux-omap@vger.kernel.org, kernel-janitors@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@kernel.org>
Subject: Re: [PATCH -next] ARM: OMAP2+: Remove duplicated include from pmic-cpcap.c
Date: Wed, 23 Oct 2019 09:59:34 -0700 [thread overview]
Message-ID: <20191023165934.GN5610@atomide.com> (raw)
In-Reply-To: <20191023062900.43576-1-yuehaibing@huawei.com>
* YueHaibing <yuehaibing@huawei.com> [191022 23:29]:
> Remove duplicated include.
Thanks applying into omap-for-v5.5/pm.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-23 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 6:29 [PATCH -next] ARM: OMAP2+: Remove duplicated include from pmic-cpcap.c YueHaibing
2019-10-23 16:59 ` 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=20191023165934.GN5610@atomide.com \
--to=tony@atomide.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=yuehaibing@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;
as well as URLs for NNTP newsgroup(s).