From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Tejun Heo <tj@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: sysfs warnings since kernel 3.13-rc1: "WARNING: ... at fs/sysfs/group.c:214 sysfs_remove_group"
Date: Sat, 11 Jan 2014 20:42:48 +0100 [thread overview]
Message-ID: <52D19EB8.9060405@googlemail.com> (raw)
In-Reply-To: <20140108183258.01c494e4@samsung.com>
Am 08.01.2014 21:32, schrieb Mauro Carvalho Chehab:
> With the patches that split em28xx-v4l from the main em28xx, this logic
> changed, as em28xx_release_analog_resources() now have another name and
> don't free em28xx dev anymore.
>
> Could you please test again after that patches?
Yes, I've tested it and the warnings are still there.
However, I just started to rework the whole em28xx resources releasing
logic and I think I know how to fix these warnings.
Regards,
Frank
prev parent reply other threads:[~2014-01-11 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 17:44 sysfs warnings since kernel 3.13-rc1: "WARNING: ... at fs/sysfs/group.c:214 sysfs_remove_group" Frank Schäfer
2014-01-07 17:59 ` Tejun Heo
2014-01-08 20:01 ` Frank Schäfer
2014-01-08 20:23 ` Greg Kroah-Hartman
2014-01-08 20:32 ` Mauro Carvalho Chehab
2014-01-11 19:42 ` Frank Schäfer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D19EB8.9060405@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox