Hi,
>
> Quoting Mark Brown (2013-12-31 08:09:16)
> > On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
> >
> > > Commit 1b1ccee1e821 "mfd: s2mps11: Fix build after regmap field rename
> > > in sec-core.c" is also touching this file, which is in Mark's tree
> > > right now. If I
Hi,
Quoting Mark Brown (2013-12-31 08:09:16)
On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
Commit 1b1ccee1e821 mfd: s2mps11: Fix build after regmap field rename
in sec-core.c is also touching this file, which is in Mark's tree
right now. If I rebase
It's
Quoting Mark Brown (2013-12-31 08:09:16)
> On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
>
> > Commit 1b1ccee1e821 "mfd: s2mps11: Fix build after regmap field rename
> > in sec-core.c" is also touching this file, which is in Mark's tree
> > right now. If I rebase
>
> It's been
On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
> Commit 1b1ccee1e821 "mfd: s2mps11: Fix build after regmap field rename
> in sec-core.c" is also touching this file, which is in Mark's tree
> right now. If I rebase
It's been in Linus' tree for a while now.
signature.asc
On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
Commit 1b1ccee1e821 mfd: s2mps11: Fix build after regmap field rename
in sec-core.c is also touching this file, which is in Mark's tree
right now. If I rebase
It's been in Linus' tree for a while now.
signature.asc
Description:
Quoting Mark Brown (2013-12-31 08:09:16)
On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
Commit 1b1ccee1e821 mfd: s2mps11: Fix build after regmap field rename
in sec-core.c is also touching this file, which is in Mark's tree
right now. If I rebase
It's been in Linus'
On 30 December 2013 03:47, Mike Turquette wrote:
> Quoting Tushar Behera (2013-12-26 02:18:58)
>> The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
>> a difference in the register offset. It would be better to update
>> existing S2MPS11 driver to support the clocks in S5M8767,
Quoting Tushar Behera (2013-12-26 02:18:58)
> The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
> a difference in the register offset. It would be better to update
> existing S2MPS11 driver to support the clocks in S5M8767, rather than
> creating an almost duplicate driver
Quoting Tushar Behera (2013-12-26 02:18:58)
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
creating an almost duplicate driver
On 30 December 2013 03:47, Mike Turquette mturque...@linaro.org wrote:
Quoting Tushar Behera (2013-12-26 02:18:58)
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
creating an almost duplicate driver altogether.
Signed-off-by: Tushar Behera
Reviewed-by:
The clocks in S2MPS11 and S5M8767 are managed in the same way, baring
a difference in the register offset. It would be better to update
existing S2MPS11 driver to support the clocks in S5M8767, rather than
creating an almost duplicate driver altogether.
Signed-off-by: Tushar Behera
12 matches
Mail list logo
