On 2016-12-02 11:51, Peter Rosin wrote:
> Anyway, at your discretion, this could be added to patch #1:
>
> Fixes: 4f5ac8cf0a11 ("pinctrl: sx150x: add support for sx1501, sx1504,
> sx1505, sx1507")
I'm apparently bad at copying, this should be:
Fixes: 4f5ac8cf0a11 ("pinctrl: sx150x: add support
On 2016-12-02 11:51, Peter Rosin wrote:
> Anyway, at your discretion, this could be added to patch #1:
>
> Fixes: 4f5ac8cf0a11 ("pinctrl: sx150x: add support for sx1501, sx1504,
> sx1505, sx1507")
I'm apparently bad at copying, this should be:
Fixes: 4f5ac8cf0a11 ("pinctrl: sx150x: add support
On Fri, Dec 2, 2016 at 11:51 AM, Peter Rosin wrote:
> I found some more issues when reading the sx150x code.
Thanks, I applied all for v4.10.
> Only the first patch actually fixes a problem. I didn't want to add a
> Fixes tag, since I don't know if commits on the pinctrl devel
On Fri, Dec 2, 2016 at 11:51 AM, Peter Rosin wrote:
> I found some more issues when reading the sx150x code.
Thanks, I applied all for v4.10.
> Only the first patch actually fixes a problem. I didn't want to add a
> Fixes tag, since I don't know if commits on the pinctrl devel branch
> are
Hi Linus!
I found some more issues when reading the sx150x code.
Only the first patch actually fixes a problem. I didn't want to add a
Fixes tag, since I don't know if commits on the pinctrl devel branch
are considered stable? Or if you perhaps want to squash this patch with
the patch it fixes?
Hi Linus!
I found some more issues when reading the sx150x code.
Only the first patch actually fixes a problem. I didn't want to add a
Fixes tag, since I don't know if commits on the pinctrl devel branch
are considered stable? Or if you perhaps want to squash this patch with
the patch it fixes?
6 matches
Mail list logo