From: santosh.shilimkar@ti•com (Santosh Shilimkar)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 1/2] ARM: Keystone SOC updates for 3.16
Date: Tue, 20 May 2014 09:40:39 -0400 [thread overview]
Message-ID: <537B5B57.2050202@ti.com> (raw)
In-Reply-To: <20140520051507.GJ18956@quad.lixom.net>
On Tuesday 20 May 2014 01:15 AM, Olof Johansson wrote:
> On Mon, May 12, 2014 at 12:41:17PM -0400, Santosh Shilimkar wrote:
>> Hi Arm-soc folks,
>>
>> Please pull below keystone SOC updates for 3.16. It merges cleanly with
>> arm-soc 'next/soc' head. As already discussed, the $subject pull request
>> has a depedency with DT dma-properties pull request [1] I sent last week
>> to be pulled into arm-soc.
>
> Hi,
>
> I didn't see a reply from Russell on that pull request yet, so I haven't
> brought it in as a dependency in case he has comments and it needs to be
> respun.
>
I pinged RMK to pull the series. After that you can pull the dependent
pull request as well as subject series. Just for wider testing purpose,
I have included the dma series in my next branch and it sitting in
linux-next for more than 2 weeks now.
> If this branch is dependent on that code, then you really need to base it on
> top of it, or else you will break bisectability. Essentially you might end up
> in a state with bisect where only these patches are applied and not the
> dependent ones.
>
I thought about that. The git objects as they exist now in pull request will
ensure that the $subject series patches appears after the dependent series.
I wanted to avoid SOC stuff to be mixed with the dma series.
Regards,
Santosh
next prev parent reply other threads:[~2014-05-20 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 16:41 [GIT PULL 1/2] ARM: Keystone SOC updates for 3.16 Santosh Shilimkar
2014-05-20 5:15 ` Olof Johansson
2014-05-20 13:40 ` Santosh Shilimkar [this message]
2014-05-23 13:47 ` Santosh Shilimkar
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=537B5B57.2050202@ti.com \
--to=santosh.shilimkar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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