public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>,
	Kevin Hilman <khilman@baylibre.com>, arm-soc <arm@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] STM32 DT changes for v4.21 #1
Date: Thu, 31 Jan 2019 09:04:52 +0100	[thread overview]
Message-ID: <85828aaa-c2f8-750f-3df0-cbded16d4a26@st.com> (raw)
In-Reply-To: <CAK8P3a05d5dMw_L=iMBT_aJaizjXuKMoiNhjj0yPTdqxMOt2VQ@mail.gmail.com>



On 1/30/19 10:01 PM, Arnd Bergmann wrote:
> On Wed, Jan 30, 2019 at 5:45 PM Alexandre Torgue
> <alexandre.torgue@st.com> wrote:
>> On 1/30/19 5:29 PM, Arnd Bergmann wrote:
>>> On Tue, Jan 8, 2019 at 9:42 AM Alexandre Torgue <alexandre.torgue@st.com> wrote:
>>>> On 1/8/19 8:29 AM, Alexandre Torgue wrote:
>>>>> On 12/3/18 12:18 PM, Alexandre Torgue wrote:
>>>>>> Hi Arnd, Olof and Kevin,
>>>>>>
>>>>>> Please consider this first round of STM32 DT updates for v4.21.
>>>>>>
>>>>>> Thanks.
>>>>>> Alex
>>>>>>
>>>>>
>>>>> This PR has not been merged in 5.0-rc1. Is there an issue (except than
>>>>> v4.21 doesn't exist :)) ?
>>>>> If not, is it possible to get it in next 5.0 rc ?
>>>>>
>>>>
>>>> Sorry for the last post. I completely missed Olof answer:
>>>>
>>>> "I think you might have missed pushing the tag to the remote?
>>>> -Olof
>>>> "
>>>>
>>>> My tag is now pushed. Is there a chance to get it in next RC ?
>>>
>>> I noticed this we were still missing this one, but it's clearly too
>>> late now for 5.0 now, so I've pulled it into arm/dt for 5.1 now.
>>
>> Sure it's too late :) and no pb. I planned to resend it for 5.1 so
>> thanks to have already taken it. One question, I have a (small) PR to
>> send for 5.1 this week. what is the best for you: base it on top of
>> arm/dt ? or rebase the one for 5.0 on 5.1 and make my PR on top of it ?
> 
> You should never rebase a branch that was already merged somewhere,
> and I also wouldn't base one of your branches on top of mine.
> 
> What I'd recommend instead is to base your new work on top of
> the branch I just pulled. If you also need stuff from 5.0-rc1, then
> start with that and merge stm32-dt-for-v4.21-1 into that, followed
> by your new work on top (note: don't merge 5.0-rc1 into
> stm32-dt-for-v4.21-1 though, that would lead to a confusing
> git history).

Ok. Thanks Arnd.

> 
>        Arnd
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-01-31  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 11:18 [GIT PULL] STM32 DT changes for v4.21 #1 Alexandre Torgue
2018-12-03 20:57 ` Olof Johansson
2019-01-08  7:29 ` Alexandre Torgue
2019-01-08  8:42   ` Alexandre Torgue
2019-01-30 16:29     ` Arnd Bergmann
2019-01-30 16:45       ` Alexandre Torgue
2019-01-30 21:01         ` Arnd Bergmann
2019-01-31  8:04           ` Alexandre Torgue [this message]

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=85828aaa-c2f8-750f-3df0-cbded16d4a26@st.com \
    --to=alexandre.torgue@st.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=olof@lixom.net \
    /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