All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hsin-hsiung Wang <hsin-hsiung.wang@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	Frank Wunderlich <frank-w@public-files.de>,
	Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Aw: Re: [PATCH] mfd: mt6397: fix probe after changing mt6397-core
Date: Mon, 7 Oct 2019 11:24:13 +0800	[thread overview]
Message-ID: <1570418653.8779.8.camel@mtksdaap41> (raw)
In-Reply-To: <3dcb030d-006e-7518-2679-48726d0c4e0e@gmail.com>

On Sat, 2019-10-05 at 10:16 +0200, Matthias Brugger wrote:
> 
> On 04/10/2019 17:51, Frank Wunderlich wrote:
> > This Question goes to Hsin-Hsiung Wang ;)
> > 
> > i only took his code (and splitted the 3rd part) to get mt6323 working again without reverting the other 2 Patches
> >> regards Frank
> > 
Hi Frank,
Sorry for the late reply.
I appreciate your help very much for splitting the code to fix the
issue.
This patch is ok for me.

> > 
> >> Gesendet: Freitag, 04. Oktober 2019 um 17:20 Uhr
> >> Von: "Lee Jones" <lee.jones@linaro.org>
> > 
> >> Will there be other devices which have a !0 CID shift?
> > 
> 
> Frank, a quick look at the series would have given you the answer.
> @Lee: yes, this change is the preparation to support MT6358:
> https://patchwork.kernel.org/patch/11110515/
> 

Hi, Lee
MT6358 uses 8 for the cid shift and I will submit next version patch of
mt6358 which is based on Frank's patch.

Hi, Matthias
Many thanks for the explanation.

> Regards,
> Matthias

WARNING: multiple messages have this Message-ID (diff)
From: Hsin-hsiung Wang <hsin-hsiung.wang@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	Frank Wunderlich <frank-w@public-files.de>,
	Lee Jones <lee.jones@linaro.org>
Cc: linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Aw: Re: [PATCH] mfd: mt6397: fix probe after changing mt6397-core
Date: Mon, 7 Oct 2019 11:24:13 +0800	[thread overview]
Message-ID: <1570418653.8779.8.camel@mtksdaap41> (raw)
In-Reply-To: <3dcb030d-006e-7518-2679-48726d0c4e0e@gmail.com>

On Sat, 2019-10-05 at 10:16 +0200, Matthias Brugger wrote:
> 
> On 04/10/2019 17:51, Frank Wunderlich wrote:
> > This Question goes to Hsin-Hsiung Wang ;)
> > 
> > i only took his code (and splitted the 3rd part) to get mt6323 working again without reverting the other 2 Patches
> >> regards Frank
> > 
Hi Frank,
Sorry for the late reply.
I appreciate your help very much for splitting the code to fix the
issue.
This patch is ok for me.

> > 
> >> Gesendet: Freitag, 04. Oktober 2019 um 17:20 Uhr
> >> Von: "Lee Jones" <lee.jones@linaro.org>
> > 
> >> Will there be other devices which have a !0 CID shift?
> > 
> 
> Frank, a quick look at the series would have given you the answer.
> @Lee: yes, this change is the preparation to support MT6358:
> https://patchwork.kernel.org/patch/11110515/
> 

Hi, Lee
MT6358 uses 8 for the cid shift and I will submit next version patch of
mt6358 which is based on Frank's patch.

Hi, Matthias
Many thanks for the explanation.

> Regards,
> Matthias



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

WARNING: multiple messages have this Message-ID (diff)
From: Hsin-hsiung Wang <hsin-hsiung.wang@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	Frank Wunderlich <frank-w@public-files.de>,
	Lee Jones <lee.jones@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Aw: Re: [PATCH] mfd: mt6397: fix probe after changing mt6397-core
Date: Mon, 7 Oct 2019 11:24:13 +0800	[thread overview]
Message-ID: <1570418653.8779.8.camel@mtksdaap41> (raw)
In-Reply-To: <3dcb030d-006e-7518-2679-48726d0c4e0e@gmail.com>

On Sat, 2019-10-05 at 10:16 +0200, Matthias Brugger wrote:
> 
> On 04/10/2019 17:51, Frank Wunderlich wrote:
> > This Question goes to Hsin-Hsiung Wang ;)
> > 
> > i only took his code (and splitted the 3rd part) to get mt6323 working again without reverting the other 2 Patches
> >> regards Frank
> > 
Hi Frank,
Sorry for the late reply.
I appreciate your help very much for splitting the code to fix the
issue.
This patch is ok for me.

> > 
> >> Gesendet: Freitag, 04. Oktober 2019 um 17:20 Uhr
> >> Von: "Lee Jones" <lee.jones@linaro.org>
> > 
> >> Will there be other devices which have a !0 CID shift?
> > 
> 
> Frank, a quick look at the series would have given you the answer.
> @Lee: yes, this change is the preparation to support MT6358:
> https://patchwork.kernel.org/patch/11110515/
> 

Hi, Lee
MT6358 uses 8 for the cid shift and I will submit next version patch of
mt6358 which is based on Frank's patch.

Hi, Matthias
Many thanks for the explanation.

> Regards,
> Matthias



  reply	other threads:[~2019-10-07  3:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 18:53 [PATCH] mfd: mt6397: fix probe after changing mt6397-core Frank Wunderlich
2019-10-03 18:53 ` Frank Wunderlich
2019-10-04 15:20 ` Lee Jones
2019-10-04 15:20   ` Lee Jones
2019-10-04 15:51   ` Aw: " Frank Wunderlich
2019-10-04 15:51     ` Frank Wunderlich
2019-10-05  8:16     ` Matthias Brugger
2019-10-05  8:16       ` Matthias Brugger
2019-10-05  8:16       ` Matthias Brugger
2019-10-07  3:24       ` Hsin-hsiung Wang [this message]
2019-10-07  3:24         ` Hsin-hsiung Wang
2019-10-07  3:24         ` Hsin-hsiung Wang
2019-10-07  3:32       ` Hsin-hsiung Wang
2019-10-07  3:32         ` Hsin-hsiung Wang
2019-10-07  3:32         ` Hsin-hsiung Wang
2019-10-09  5:19   ` Frank Wunderlich
2019-10-09  5:19     ` Frank Wunderlich
2019-10-09  5:19     ` Frank Wunderlich
2019-10-16  9:53 ` Lee Jones
2019-10-16  9:53   ` Lee Jones
2019-10-16  9:53   ` Lee Jones
2019-10-22  9:46   ` Frank Wunderlich
2019-10-22  9:46     ` Frank Wunderlich
2019-10-22  9:46     ` Frank Wunderlich
2019-10-24  7:57     ` Lee Jones
2019-10-24  7:57       ` Lee Jones
2019-10-24  7:57       ` Lee Jones

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=1570418653.8779.8.camel@mtksdaap41 \
    --to=hsin-hsiung.wang@mediatek.com \
    --cc=frank-w@public-files.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.