From: Nikhil M Jain <n-jain1@ti.com>
To: Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <devarsht@ti.com>, <vigneshr@ti.com>,
<nsekhar@ti.com>, <sjg@chromium.org>
Subject: Re: [PATCH V2 0/2] Fix warnings occurred during compilation
Date: Thu, 20 Jul 2023 11:35:10 +0530 [thread overview]
Message-ID: <bd0da766-e6ac-abd8-a2b7-1d6b802caf09@ti.com> (raw)
In-Reply-To: <20230719131802.GU1670569@bill-the-cat>
Hi Tom,
On 19/07/23 18:48, Tom Rini wrote:
> On Wed, Jul 19, 2023 at 06:44:18PM +0530, Nikhil M Jain wrote:
>> Hi Tom,
>>
>> On 19/07/23 17:28, Tom Rini wrote:
>>> On Wed, Jul 19, 2023 at 04:44:36PM +0530, Nikhil M Jain wrote:
>>>> Hi Tom,
>>>>
>>>> Seems like this series fell through the cracks, so a gentle reminder on
>>>> this.
>>>>
>>>> On 21/06/23 16:29, Nikhil M Jain wrote:
>>>>> This patch series aims at fixing warnings which occur during
>>>>> compilation, by including required header files and using appropriate
>>>>> types for variables which are typecasted.
>>>>>
>>>>> Changes in V2:
>>>>> - Type cast bmp_load_addr to uintptr_t at places necessary rather than
>>>>> changing argument type.
>>>>>
>>>>> Nikhil M Jain (2):
>>>>> board: ti: am62x: evm: Include necessary header files
>>>>> common: splash_source: Fix type casting errors.
>>>>>
>>>>> board/ti/am62x/evm.c | 1 +
>>>>> common/splash_source.c | 6 +++---
>>>>> 2 files changed, 4 insertions(+), 3 deletions(-)
>>>
>>> This depends on the other series that you just reposted I believe you
>>> had said before.
>>>
>>
>> This series is independent and doesn't depend on the series I have
>> reposted yesterday.
>
> What is it against then? It didn't apply before, I could have sworn I
> reported.
>
I have checked, these patches can be applied on tip of next
independently. Below are the logs.
[1] https://gist.github.com/NikMJain/336831817fc79d6bf3d512d6d2663d59
Thanks,
Nikhil
prev parent reply other threads:[~2023-07-20 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 10:59 [PATCH V2 0/2] Fix warnings occurred during compilation Nikhil M Jain
2023-06-21 10:59 ` [PATCH V2 1/2] board: ti: am62x: evm: Include necessary header files Nikhil M Jain
2023-07-21 23:34 ` Tom Rini
2023-06-21 10:59 ` [PATCH V2 2/2] common: splash_source: Fix type casting errors Nikhil M Jain
2023-07-21 23:34 ` Tom Rini
2023-07-19 11:14 ` [PATCH V2 0/2] Fix warnings occurred during compilation Nikhil M Jain
2023-07-19 11:58 ` Tom Rini
2023-07-19 13:14 ` [EXTERNAL] " Nikhil M Jain
2023-07-19 13:18 ` Tom Rini
2023-07-20 6:05 ` Nikhil M Jain [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=bd0da766-e6ac-abd8-a2b7-1d6b802caf09@ti.com \
--to=n-jain1@ti.com \
--cc=devarsht@ti.com \
--cc=nsekhar@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@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