From: Andrew Lunn <andrew@lunn.ch>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Paul Cercueil <paul@crapouillou.net>,
"David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Mathieu Malaterre <malat@debian.org>
Subject: Re: [PATCH] net: ethernet: dm9000: Handle -EPROBE_DEFER in dm9000_parse_dt()
Date: Mon, 17 Feb 2020 13:59:53 +0100 [thread overview]
Message-ID: <20200217125953.GD32734@lunn.ch> (raw)
In-Reply-To: <1513E253-0E58-4088-84E2-E35F3067BB4B@goldelico.com>
> Is the EPROBE_DEFER mechanism also working for drivers
> fully compiled into the kernel (I may have been mislead
> since EPROBE_DEFER patches are almost always done to make
> drivers work as modules)?
Yes. It is a generic mechanism and used with all driver probe
functions.
Andrew
prev parent reply other threads:[~2020-02-17 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 19:39 [PATCH] net: ethernet: dm9000: Handle -EPROBE_DEFER in dm9000_parse_dt() Paul Cercueil
2020-02-16 19:58 ` Andrew Lunn
2020-02-17 4:02 ` David Miller
2020-02-17 10:04 ` H. Nikolaus Schaller
2020-02-17 12:59 ` Andrew Lunn [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=20200217125953.GD32734@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malat@debian.org \
--cc=netdev@vger.kernel.org \
--cc=paul@crapouillou.net \
/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).