From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hsin-hsiung Wang Subject: Re: Aw: Re: [BUG] [PATCH v5 02/10] mfd: mt6397: extract irq related code from core driver Date: Thu, 29 Aug 2019 14:24:36 +0800 Message-ID: <1567059876.15320.3.camel@mtksdaap41> References: <1566531931-9772-1-git-send-email-hsin-hsiung.wang@mediatek.com> <1566531931-9772-3-git-send-email-hsin-hsiung.wang@mediatek.com> <0A87F427-2D81-412A-9549-09A51A021799@public-files.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Frank Wunderlich , Matthias Brugger Cc: linux-mediatek@lists.infradead.org, Mark Rutland , Alessandro Zummo , Alexandre Belloni , srv_heupstream@mediatek.com, devicetree@vger.kernel.org, Greg Kroah-Hartman , Sean Wang , Liam Girdwood , Rob Herring , linux-kernel@vger.kernel.org, Richard Fontana , Mark Brown , linux-arm-kernel@lists.infradead.org, "=?ISO-8859-1?Q?=22Ren=E9?= van Dorst\"" , Thomas Gleixner , Eddie Huang , Lee Jones , Kate Stewart List-Id: devicetree@vger.kernel.org Hi Frank/Matthias, On Fri, 2019-08-23 at 19:16 +0200, Frank Wunderlich wrote: > > Gesendet: Freitag, 23. August 2019 um 17:42 Uhr > > Von: "Matthias Brugger" > > > I suppose that's because 3/10 has code that should be in 2/10 and for some > > reason 3/10 was not pushed for linux-next inclusion. Although it has the same > > Acked-for-mfd-by tag. > > > > @Frank, can you test if adding 3/10 to your code base fixes the issue? > > adding part 3 [1] seems to fix the issue too > > [ 4.960051] mt6323-regulator mt6323-regulator: Chip ID = 0x2023 > > thanks > > [1] https://patchwork.kernel.org/patch/11110509/ Thanks for your comments. The root cause seems I didn't split the code well. I will fix it in the next version.