Hello Andy
On 2/13/24 13:55, Andy Shevchenko wrote:
On Tue, Feb 13, 2024 at 2:14 AM George Stark wrote:
Hello Andy
On 2/12/24 12:53, Andy Shevchenko wrote:
On Mon, Feb 12, 2024 at 1:52 AM George Stark wrote:
I haven't lose hope for the devm_mutex thing and keep pinging those guys
from
On Tue, Feb 13, 2024 at 2:14 AM George Stark wrote:
>
> Hello Andy
>
> On 2/12/24 12:53, Andy Shevchenko wrote:
> > On Mon, Feb 12, 2024 at 1:52 AM George Stark
> > wrote:
> >> I haven't lose hope for the devm_mutex thing and keep pinging those guys
> >> from time to time.
> >
> > I don't
Hello Andy
On 2/12/24 12:53, Andy Shevchenko wrote:
On Mon, Feb 12, 2024 at 1:52 AM George Stark wrote:
I haven't lose hope for the devm_mutex thing and keep pinging those guys
from time to time.
I don't understand. According to v4 thread Christophe proposed on how
the patch should look
On Mon, Feb 12, 2024 at 1:52 AM George Stark wrote:
> I haven't lose hope for the devm_mutex thing and keep pinging those guys
> from time to time.
I don't understand. According to v4 thread Christophe proposed on how
the patch should look like. What you need is to incorporate an updated
version
Hello Andy.
I haven't lose hope for the devm_mutex thing and keep pinging those guys
from time to time.
Sure I can single out the fix-only patch I'll do it tomorrow.
On 2/9/24 20:11, Andy Shevchenko wrote:
On Thu, Dec 21, 2023 at 03:11:11PM +, Lee Jones wrote:
On Thu, 14 Dec 2023,
On Thu, Dec 14, 2023 at 08:36:04PM +0300, George Stark wrote:
> This patch series fixes the problem of devm_led_classdev_register misusing.
>
> The basic problem is described in [1]. Shortly when
> devm_led_classdev_register()
> is used then led_classdev_unregister() called after driver's
On Thu, Dec 21, 2023 at 03:11:11PM +, Lee Jones wrote:
> On Thu, 14 Dec 2023, George Stark wrote:
>
> > This patch series fixes the problem of devm_led_classdev_register misusing.
> >
> > The basic problem is described in [1]. Shortly when
> > devm_led_classdev_register()
> > is used then
On Thu, 14 Dec 2023, George Stark wrote:
> This patch series fixes the problem of devm_led_classdev_register misusing.
>
> The basic problem is described in [1]. Shortly when
> devm_led_classdev_register()
> is used then led_classdev_unregister() called after driver's remove()
> callback.
>
This patch series fixes the problem of devm_led_classdev_register misusing.
The basic problem is described in [1]. Shortly when devm_led_classdev_register()
is used then led_classdev_unregister() called after driver's remove() callback.
led_classdev_unregister() calls driver's brightness_set
