Messages in this thread | | | Subject | Re: gigaset: freeing an active object | From | Tilman Schmidt <> | Date | Mon, 7 Dec 2015 19:40:55 +0100 |
| |
Am 07.12.2015 um 13:25 schrieb Paul Bolle:
>>> Otherwise we'd still be freeing memory >>> managed through reference counting. >> >> Now I#m confused. I thought by following Peter's suggestion to put the >> kfree() in the release method we'd avoid just that. > > Apparently it does, because I can't trigger the WARNING we're discussing > here with your patch applied.
Nice.
> I'll have to dive into this stuff again, > because apparently my mental model of what's going on is incomplete at > best.
I won't claim anything like completeness for mine.
> In the mean time you might want to turn your patch into something that > can actually be applied (with or without my Sign-off or Ack; I don't > care how it finds its way into the tree). Please add add > Fixes: 2869b23e4b95 ("[PATCH] drivers/isdn/gigaset: new M101 driver (v2)")
Will do. (Not today, though.)
Regards, Tilman
-- Tilman Schmidt E-Mail: tilman@imap.cc Bonn, Germany Nous, on a des fleurs et des bougies pour nous protéger.
[unhandled content-type:application/pgp-signature] | |