From: Alexandre Torgue <alexandre.torgue@st.com>
To: Olof Johansson <olof@lixom.net>
Cc: Patrice CHOTARD <patrice.chotard@st.com>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: ARM: multi_v7_defconfig: Enable SPI_STM32_QSPI support
Date: Wed, 31 Jul 2019 16:40:17 +0200 [thread overview]
Message-ID: <ce2b0a2f-6775-1318-1537-eae3ad4e63fd@st.com> (raw)
In-Reply-To: <CAOesGMirq=42Cj4kT=dLSqUiG-yee5zuqFhg5t=ud5KPmQJYBw@mail.gmail.com>
On 7/31/19 3:21 PM, Olof Johansson wrote:
> On Wed, Jul 31, 2019 at 3:20 PM Olof Johansson <olof@lixom.net> wrote:
>>
>> Hi,
>>
>> On Wed, Jul 31, 2019 at 8:48 AM Alexandre Torgue
>> <alexandre.torgue@st.com> wrote:
>>>
>>> Hi Olof
>>>
>>> On 7/30/19 7:36 PM, Olof Johansson wrote:
>>>> Hi Patrice,
>>>>
>>>> If you cc soc@kernel.org on patches you want us to apply, you'll get
>>>> them automatically tracked by patchwork.
>>>>
>>>
>>> Does it means that you will take it directly in arm-soc tree ?
>>> I mean, I used to take this kind of patch (multi-v7_defconfig patch
>>> linked to STM32 driver) in my stm32 branch and to send PR for them.
>>
>> You can do that too -- it was unclear to me whether you posted the
>> patch with us in the To: line because you wanted it applied or not.
>
> Also, we request that platform maintainers keep the defconfig updates
> in a separate branch, since we normally track them in a separate
> branch on our side. So if you do it in the future, please send
> separate PR.
>
> For single patches, it's just as easy to send us the patch as a pull request.
>
Ok. So I'll continue as I did :)
Thanks for clarifications
Alex
>
> Thanks,
>
> -Olof
>
next prev parent reply other threads:[~2019-07-31 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 13:55 ARM: multi_v7_defconfig: Enable SPI_STM32_QSPI support patrice.chotard
2019-07-30 17:36 ` Olof Johansson
2019-07-31 6:47 ` Alexandre Torgue
2019-07-31 13:20 ` Olof Johansson
2019-07-31 13:21 ` Olof Johansson
2019-07-31 14:40 ` Alexandre Torgue [this message]
2019-07-31 7:15 ` Patrice CHOTARD
2019-07-31 7:22 patrice.chotard
2019-08-02 7:38 ` Alexandre Torgue
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=ce2b0a2f-6775-1318-1537-eae3ad4e63fd@st.com \
--to=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=olof@lixom.net \
--cc=patrice.chotard@st.com \
/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).