From: Tony Lindgren <tony@atomide.com>
To: Keerthy <j-keerthy@ti.com>
Cc: d-gerlach@ti.com, linux-kernel@vger.kernel.org, t-kristo@ti.com,
linux-arm-kernel@lists.infradead.org, ssantosh@kernel.org,
dan.carpenter@oracle.com
Subject: Re: [PATCH] soc: ti: pm33xx: Fix static checker warnings
Date: Tue, 13 Aug 2019 05:04:53 -0700 [thread overview]
Message-ID: <20190813120453.GW52127@atomide.com> (raw)
In-Reply-To: <20190626075014.2911-1-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [190626 00:50]:
> The patch fixes a bunch of static checker warnings.
Sorry I just noticed that this one is still pending, applying
into fixes.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-13 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 7:50 [PATCH] soc: ti: pm33xx: Fix static checker warnings Keerthy
2019-08-13 12:04 ` Tony Lindgren [this message]
2019-08-13 12:10 ` Keerthy
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=20190813120453.GW52127@atomide.com \
--to=tony@atomide.com \
--cc=d-gerlach@ti.com \
--cc=dan.carpenter@oracle.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.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).