kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: where and when the kernel destroy devices memory if there were no matched driver for it?
Date: Wed, 27 Jun 2018 13:57:11 +0800	[thread overview]
Message-ID: <20180627055711.GA16232@kroah.com> (raw)
In-Reply-To: <563a11f9-f027-73b4-fa88-f51354ce02b3@163.com>

On Wed, Jun 27, 2018 at 01:52:55PM +0800, kipade wrote:
> Hi, all
> 
> As my question, would kernel destroy deivces struct if there were no matched
> driver attached on it?

No, only when the device is removed from the system does that structure
get destroyed.

greg k-h

  reply	other threads:[~2018-06-27  5:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 14:14 clk: timestamps Subhashini Rao Beerisetty
2018-06-27  5:52 ` where and when the kernel destroy devices memory if there were no matched driver for it? kipade
2018-06-27  5:57   ` Greg KH [this message]
2018-06-27  8:57     ` kipade
2018-06-27 12:06       ` Greg KH
2018-06-27  7:47 ` clk: timestamps Yann Droneaud
2018-06-27  8:42   ` Subhashini Rao Beerisetty
2018-06-27 20:50 ` valdis.kletnieks at vt.edu

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=20180627055711.GA16232@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).