From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] ARM: davinci: SoC updates for v3.10 (part 2)
Date: Tue, 16 Apr 2013 09:48:38 -0700 [thread overview]
Message-ID: <20130416164838.GE4918@quad.lixom.net> (raw)
In-Reply-To: <516CEBCF.60507@ti.com>
On Tue, Apr 16, 2013 at 11:42:31AM +0530, Sekhar Nori wrote:
> On 4/16/2013 1:48 AM, Olof Johansson wrote:
> > On Mon, Apr 15, 2013 at 10:53:18PM +0530, Sekhar Nori wrote:
> >> Hi Arnd, Olof,
> >>
> >> Can you please the following SoC updates for DaVinci.
> >> The branch depends on (and merges) an immutable branch
> >> from Ohad adding DA8XX rempote proc driver.
> >
> > Hi,
> >
> > Where is this branch from? Git URL and branch name, please -- we prefer to pull
> > these in as separate branches under depends/* as well to document it.
>
> Here is the repo and branch:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git for-next
Oh! Looking at that branch, and the new branch from you, I don't actually see
a dependency between them. Sure, the Davinci mach-side code registers a new
device, but until the driver has the corresponding changes, there's no breakage
caused by the new registration. There are no new data structures introduced
either, so there's no build-time dependency added.
So it would be just as easy to just merge this as a nondependent branch. When
both sides of the change land, remoteproc will work. But until then, nothing
existing will be broken.
Sound ok? If so, please just rebase your 4 patches on top of the old SoC branch
without the dependency and send a fresh pull request, please. :)
-Olof
next prev parent reply other threads:[~2013-04-16 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 17:23 [GIT PULL 1/3] ARM: davinci: DT updates for v3.10 (part 2) Sekhar Nori
2013-04-15 17:23 ` [GIT PULL 2/3] ARM: davinci: SoC " Sekhar Nori
2013-04-15 20:18 ` Olof Johansson
2013-04-16 6:12 ` Sekhar Nori
2013-04-16 16:48 ` Olof Johansson [this message]
2013-04-17 14:15 ` Sekhar Nori
2013-04-15 17:23 ` [GIT PULL 3/3] ARM: davinci: board " Sekhar Nori
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=20130416164838.GE4918@quad.lixom.net \
--to=olof@lixom.net \
--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 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).