From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull-request: u-boot-spi/master
Date: Fri, 9 Oct 2015 15:55:56 +0200 [thread overview]
Message-ID: <5617C76C.70209@xilinx.com> (raw)
In-Reply-To: <20151009135425.GR3829@bill-the-cat>
Hi Tom,
On 10/09/2015 03:54 PM, Tom Rini wrote:
> On Fri, Oct 09, 2015 at 03:47:59PM +0200, Michal Simek wrote:
>> Hi Jagan,
>>
>> On 09/30/2015 12:23 AM, Michal Simek wrote:
>>> On 09/29/2015 11:13 PM, Jagan Teki wrote:
>>>> On 21 September 2015 at 23:56, Jagan Teki <jteki@openedev.com> wrote:
>>>>> Hi Michal,
>>>>>
>>>>> On 19 September 2015 at 06:38, Michal Simek <michal.simek@xilinx.com> wrote:
>>>>>> On 09/19/2015 02:55 AM, Michal Simek wrote:
>>>>>>> On 09/16/2015 09:20 AM, Jagan Teki wrote:
>>>>>>>> Hi Michal,
>>>>>>>>
>>>>>>>> On 15 September 2015 at 18:58, Simon Glass <sjg@chromium.org> wrote:
>>>>>>>>> Hi Jagan,
>>>>>>>>>
>>>>>>>>> On 15 September 2015 at 02:13, Jagan Teki <jteki@openedev.com> wrote:
>>>>>>>>>> Hi Tom,
>>>>>>>>>>
>>>>>>>>>> Zynq patches has SPL build dependency with Simon changes [1].
>>>>>>>>>>
>>>>>>>>>> Simon, Any plan to send a PR for your changes.
>>>>>>>>>>
>>>>>>>>>> [1] http://git.denx.de/?p=u-boot/u-boot-dm.git;a=shortlog;h=refs/heads/zynq-working
>>>>>>>>>
>>>>>>>>> These are for the zynq maintainer I think. They are not assigned to me
>>>>>>>>> in patchwork.
>>>>>>>>
>>>>>>>> Seems like this patch[1] resolves the SPL build issue, any plan on
>>>>>>>> pushing this? of-course I will test this and let you know.
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] http://git.denx.de/?p=u-boot/u-boot-dm.git;a=commitdiff;h=7916a8cf902177afd20a09527a9cf307622bb6d2
>>>>>>>
>>>>>>> Simon: Are you going to push it? Or do you want me to collect all of
>>>>>>> these zynq/zynqmp patches?
>>>>>>
>>>>>> Sorry I have read Simon's reaction after. I will try to collect all
>>>>>> these zynq patches and will send pull request.
>>>>>
>>>>> Please send your PR on top of these changes, and let me know for any inputs.
>>>>
>>>> Seems like Michal is busy with something, Shall I go with build fix
>>>> (not sure whether it's working SPI-SPL or not)
>>>
>>> Next week I will look at it.
>>
>> All your patches will go on the top of zynq/zynqmp patches and the merge
>> will happen after 2015.10.
>> Is there any particular reason to push these changes before 2015.10?
>
> I had/have been holding this for after the merge window. If there are
> any release-critical fixes in the SPI tree they need to be put into a
> separate pull request asap. Thanks!
Good. I was talking to Simon yesterday and retest zynq and zynqmp SPL DM
changes which should go first to your tree and then these spi changes
should go on the top.
Thanks,
Michal
next prev parent reply other threads:[~2015-10-09 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 8:13 [U-Boot] Pull-request: u-boot-spi/master Jagan Teki
2015-09-15 13:28 ` Simon Glass
2015-09-16 7:20 ` Jagan Teki
2015-09-19 0:55 ` Michal Simek
2015-09-19 1:08 ` Michal Simek
2015-09-21 18:26 ` Jagan Teki
2015-09-29 21:13 ` Jagan Teki
2015-09-29 22:23 ` Michal Simek
2015-10-09 13:47 ` Michal Simek
2015-10-09 13:54 ` Tom Rini
2015-10-09 13:55 ` Michal Simek [this message]
2015-10-11 11:26 ` Jagan Teki
-- strict thread matches above, loose matches on Subject: below --
2015-10-11 11:22 Jagan Teki
2015-10-12 15:14 ` Tom Rini
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=5617C76C.70209@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.de \
/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