From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Borislav Petkov <bp@alien8.de>
Cc: mchehab@kernel.org, tony@atomide.com,
Tero Kristo <t-kristo@ti.com>,
ssantosh@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org
Subject: Re: [PATCHv3 2/3] EDAC: ti: add support for TI keystone and DRA7xx EDAC
Date: Mon, 13 Nov 2017 10:04:09 -0800 [thread overview]
Message-ID: <f9d1b261-7942-6ff6-bfc3-4b3ff22f0e27@oracle.com> (raw)
In-Reply-To: <20171113175816.qmvbug4kf3qu5meq@pd.tnic>
On 11/13/2017 9:58 AM, Borislav Petkov wrote:
> On Mon, Nov 13, 2017 at 09:10:09AM -0800, Santosh Shilimkar wrote:
>> Once you have driver queued up, please post DTS patches
>> separately. Will queue them up.
>
> It would be easier if you ACK the DTS patches and I can pick all three
> up after the merge window is over. This way they go together and there's
> no inter-tree dependency.
>
That doesn't help and not an usual workflow.
DTS patches actually conflict and they better go through arch port.
Let the driver get merged which has no dependency with DTS patches
instead of waiting for merge window being over. DTS patches can be
merged anytime once its respective driver are in tree.
Regards,
Santosh
next prev parent reply other threads:[~2017-11-13 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 20:38 [PATCH 0/3] EDAC: TI: add support for DRA7 and keystone EDAC Tero Kristo
2017-11-07 20:38 ` [PATCH 1/3] Documentation: dt: memory: ti-emif: add edac support under emif Tero Kristo
2017-11-10 8:25 ` [PATCHv2 2/3] EDAC: ti: add support for TI keystone and DRA7xx EDAC Tero Kristo
2017-11-11 10:46 ` Borislav Petkov
2017-11-13 9:03 ` Tero Kristo
[not found] ` <1510087139-21885-2-git-send-email-t-kristo-l0cyMroinI0@public.gmane.org>
2017-12-07 9:03 ` [PATCH 1/3] Documentation: dt: memory: ti-emif: add edac support under emif Tero Kristo
2017-11-07 20:38 ` [PATCH 2/3] EDAC: ti: add support for TI keystone and DRA7xx EDAC Tero Kristo
2017-11-09 10:14 ` Borislav Petkov
2017-11-09 10:38 ` Tero Kristo
2017-11-09 12:12 ` Borislav Petkov
2017-11-09 11:50 ` Jan Lübbe
2017-11-09 12:40 ` Tero Kristo
2017-11-13 13:08 ` [PATCHv3 " Tero Kristo
2017-11-13 17:10 ` Santosh Shilimkar
2017-11-13 17:58 ` Borislav Petkov
2017-11-13 18:04 ` Santosh Shilimkar [this message]
2017-11-13 18:08 ` Borislav Petkov
2017-11-13 18:49 ` Tero Kristo
2017-11-13 19:17 ` Santosh Shilimkar
2017-11-27 13:12 ` Borislav Petkov
2017-11-07 20:38 ` [PATCH 3/3] ARM: dts: Keystone: add ECC error handler support Tero Kristo
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=f9d1b261-7942-6ff6-bfc3-4b3ff22f0e27@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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