[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3476571.0yU9yvPsKF@linux-gy6r.site>
Date: Mon, 25 Jan 2016 19:44:01 +0100
From: Matthias Brugger <matthias.bgg@...il.com>
To: John Crispin <blogic@...nwrt.org>
Cc: Lee Jones <lee.jones@...aro.org>, Flora Fu <flora.fu@...iatek.com>,
Sascha Hauer <s.hauer@...gutronix.de>,
Henry Chen <henryc.chen@...iatek.com>,
Steven Liu <steven.liu@...iatek.com>,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 4/4] mfd: mediatek: add MT6323 support to MT6397 driver
On Monday 25 Jan 2016 16:36:40 John Crispin wrote:
> Hi,
>
> On 25/01/2016 13:41, Lee Jones wrote:
> > Please honour the subject format of the subsystem you are contributing
> > to.
> >
> > `git log --oneline -- $subsystem` gives you this.
> >
> > On Mon, 25 Jan 2016, John Crispin wrote:
> >> Signed-off-by: John Crispin <blogic@...nwrt.org>
> >> ---
>
> [...]
>
> >> @@ -261,6 +271,15 @@ static int mt6397_probe(struct platform_device
> >> *pdev)
> >>
> >> }
> >>
> >> switch (id & 0xff) {
> >>
> >> + case MT6323_CID_CODE:
> >> + mt6397->int_con[0] = MT6323_INT_CON0;
> >
> > This is confusing. You're still using memory allocated for a mt6397
> > device.
>
> the variable is currently defined as struct mt6397_chip *mt6397;
> shall i only change the name or also create a patch to rename the struct ?
>
I think we should rename the struct and the file as well.
Cheers,
Matthias
Powered by blists - more mailing lists