public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] STM32 defconfig changes for v4.19 #1
Date: Mon, 16 Jul 2018 13:55:06 +0200	[thread overview]
Message-ID: <9c9d4951-eccb-5285-d98a-a9172d2b1eab@st.com> (raw)
In-Reply-To: <20180714213148.h2f3ipw6bja36x4p@localhost>

Hi Olof

On 07/14/2018 11:31 PM, Olof Johansson wrote:
> On Fri, Jul 13, 2018 at 04:01:40PM +0200, Alexandre Torgue wrote:
>> Hi Arnd, Olof and Kevin,
>>
>> Please consider this first round of STM32 defconfig updates for v4.19.
>> This time it concerns only multi_v7_defconfig.
>>
>> Thanks.
>> Alex
>>
>> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>>
>>    Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>>
>> are available in the git repository at:
>>
>>    git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git
>> tags/stm32-defconfig-for-v4.19-1
>>
>> for you to fetch changes up to 1b8a8589a3e10997fa8f43e7da874c4903f33ac7:
>>
>>    ARM: multi_v7_defconfig: enable STM32 DCMI media support (2018-07-13
>> 14:54:24 +0200)
> 
> Hi,
> 
> We renormalized the multi_v7_defconfig file in 4.18-rc3, so this pull request
> has quite a few conflicts due to that. I've fixed it up though, make sure it's
> behaving like you would expect.

I checked merge point on arm-soc tree and for me it's correct.

Thanks
Alex


> 
> Thanks,
> 
> 
> -Olof
> 

      reply	other threads:[~2018-07-16 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 14:01 [GIT PULL] STM32 defconfig changes for v4.19 #1 Alexandre Torgue
2018-07-14 21:31 ` Olof Johansson
2018-07-16 11:55   ` 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=9c9d4951-eccb-5285-d98a-a9172d2b1eab@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