From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] STM32 DT changes for v4.11 #1
Date: Fri, 20 Jan 2017 12:06:13 +0100 [thread overview]
Message-ID: <ff7fb3d8-d4bc-701e-6c80-b91f4e23b412@st.com> (raw)
In-Reply-To: <CAK8P3a24uSmOYdhJQD2gE8qunb_ObXQ1zg8MAbzpPy5OR25-Qw@mail.gmail.com>
On 01/20/2017 11:30 AM, Arnd Bergmann wrote:
> On Tue, Jan 17, 2017 at 7:53 AM, Olof Johansson <olof@lixom.net> wrote:
>> On Mon, Jan 16, 2017 at 04:49:29PM +0100, Alexandre Torgue wrote:
>>> -----
>>> First patch "clk: stm32f4: Update DT bindings documentation")
>>> has already been merged in clock tree.
>>
>> Ugh. That patch doesn't just update documentation. It also updates the
>> dt-include file.
>>
>> So, if it's already been merged into the clock tree, then we can't merge
>> a separate copy here.
>>
>> By now, easiest is to hold off making use of it until it's on a shared
>> branch, i.e. next release. Use the numerical values until then.
>
> I suggested doing it this way if the same commit ID could be used rather
> than having two identical commits with different IDs in the two branches,
> which would be bad practice.
>
> Alexandre, can you clarify whether this is the same commit ID on both
> branches, and whether the tree it was merged into is one that does
> not get rebased?
Actually, commit SHA1 are different in clk tree and stm32-dt tree.
Do I need to "re-build" my branch based on 4.10-rc1 + "dt bindings patch
with clk (with the same sha1 than in clock tree) " ?
Alex
>
> Arnd
>
next prev parent reply other threads:[~2017-01-20 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 15:49 [GIT PULL] STM32 DT changes for v4.11 #1 Alexandre Torgue
2017-01-17 6:53 ` Olof Johansson
2017-01-17 8:42 ` Alexandre Torgue
2017-01-20 10:30 ` Arnd Bergmann
2017-01-20 11:06 ` Alexandre Torgue [this message]
2017-01-20 11:55 ` Arnd Bergmann
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=ff7fb3d8-d4bc-701e-6c80-b91f4e23b412@st.com \
--to=alexandre.torgue@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox