From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log
Date: Wed, 16 Sep 2015 12:13:37 -0700 [thread overview]
Message-ID: <55F9BF61.4080200@oracle.com> (raw)
In-Reply-To: <55F9A05E.4090000@ti.com>
On 9/16/2015 10:01 AM, Murali Karicheri wrote:
> On 09/15/2015 05:20 PM, santosh shilimkar wrote:
>> On 9/15/2015 11:14 AM, Murali Karicheri wrote:
>>> On 09/09/2015 12:38 PM, Murali Karicheri wrote:
[..]
>>> Santosh,
>>>
>>> I have checked v4.3-rc1 and I don't see it. Did you send the pull
>>> request?
>>>
>> They are in the queue fo 4.4-rc1. They were too late for 4.3.
>> You might know already, typically as a rule of thumb followed
>> on arm-soc, we need to get patches reviewed/acked by rc4 to make
>> it for next merge window.
>> Ofcourse genuine bug fixes can make it to the same cycle.
> Is there a branch where you have applied the patches that you can
> provide me? I want to send it to internal list for merge.
>
Yes. I will push it out later this week. Will drop you
note when I do that.
WARNING: multiple messages have this Message-ID (diff)
From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Murali Karicheri <m-karicheri2@ti.com>,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, ssantosh@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log
Date: Wed, 16 Sep 2015 12:13:37 -0700 [thread overview]
Message-ID: <55F9BF61.4080200@oracle.com> (raw)
In-Reply-To: <55F9A05E.4090000@ti.com>
On 9/16/2015 10:01 AM, Murali Karicheri wrote:
> On 09/15/2015 05:20 PM, santosh shilimkar wrote:
>> On 9/15/2015 11:14 AM, Murali Karicheri wrote:
>>> On 09/09/2015 12:38 PM, Murali Karicheri wrote:
[..]
>>> Santosh,
>>>
>>> I have checked v4.3-rc1 and I don't see it. Did you send the pull
>>> request?
>>>
>> They are in the queue fo 4.4-rc1. They were too late for 4.3.
>> You might know already, typically as a rule of thumb followed
>> on arm-soc, we need to get patches reviewed/acked by rc4 to make
>> it for next merge window.
>> Ofcourse genuine bug fixes can make it to the same cycle.
> Is there a branch where you have applied the patches that you can
> provide me? I want to send it to internal list for merge.
>
Yes. I will push it out later this week. Will drop you
note when I do that.
next prev parent reply other threads:[~2015-09-16 19:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 21:46 [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log Murali Karicheri
2015-09-04 21:46 ` Murali Karicheri
2015-09-04 21:46 ` Murali Karicheri
2015-09-04 21:46 ` [PATCH v1 2/2] ARM: dts: keystone: enable accumulator channels Murali Karicheri
2015-09-04 21:46 ` Murali Karicheri
2015-09-04 21:46 ` Murali Karicheri
2015-09-05 3:53 ` [PATCH v1 1/2] soc: ti: display firmware file name as part of boot log santosh.shilimkar at oracle.com
2015-09-05 3:53 ` santosh.shilimkar
2015-09-09 16:38 ` Murali Karicheri
2015-09-09 16:38 ` Murali Karicheri
2015-09-09 16:38 ` Murali Karicheri
2015-09-09 17:12 ` santosh.shilimkar at oracle.com
2015-09-09 17:12 ` santosh.shilimkar
2015-09-09 17:23 ` Murali Karicheri
2015-09-09 17:23 ` Murali Karicheri
2015-09-09 17:23 ` Murali Karicheri
2015-09-15 18:14 ` Murali Karicheri
2015-09-15 18:14 ` Murali Karicheri
2015-09-15 18:14 ` Murali Karicheri
2015-09-15 21:20 ` santosh shilimkar
2015-09-15 21:20 ` santosh shilimkar
2015-09-16 17:01 ` Murali Karicheri
2015-09-16 17:01 ` Murali Karicheri
2015-09-16 17:01 ` Murali Karicheri
2015-09-16 19:13 ` santosh shilimkar [this message]
2015-09-16 19:13 ` santosh shilimkar
2015-09-17 16:18 ` santosh.shilimkar at oracle.com
2015-09-17 16:18 ` santosh.shilimkar
2015-09-17 16:18 ` santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA
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=55F9BF61.4080200@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.