From: "Alexander Shiyan" <shc_work-JGs/UdohzUI@public.gmane.org>
To: "Mark Brown" <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "Axel Lin" <axel.lin-8E1dMatC8ynQT0dZR+AlfA@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi: clps711x: Add MODULE_ALIAS to support module auto-loading
Date: Tue, 14 Jan 2014 22:04:27 +0400 [thread overview]
Message-ID: <1389722667.687082955@f317.i.mail.ru> (raw)
In-Reply-To: <20140114180048.GU15567-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 945 bytes --]
ÐÑоÑник, 14 ÑнваÑÑ 2014, 18:00 UTC Ð¾Ñ Mark Brown <broonie@kernel.org>:
> On Tue, Jan 14, 2014 at 09:58:31PM +0400, Alexander Shiyan wrote:
> > ÐÑоÑник, 14 ÑнваÑÑ 2014, 17:41 UTC Ð¾Ñ Mark Brown <broonie@kernel.org>:
>
> > > I can't parse the above sorry? If you're asking how inter module
> > > dependencies get resolved the module loader does this automatically
> > > based on the symbols referenced in modules.
>
> > Yes, but there are no modules that have clps711x-spi dependency.
> > I am not guru in module handling, just want to understand the need
> > to make this change.
>
> It's so that if the driver is built as a module if the device is present
> in the system userspace can figure out which module to load to support
> it.
OK, if so this makes sense. Thank you.
---
N§²æìr¸yúèØb²X¬¶Ç§vØ^)Þº{.nÇ+·¥{±²¢Ø^nr¡ö¦zË\x1aëh¨èÚ&¢îý»\x05ËÛÔØï¦v¬Îf\x1dp)¹¹br ê+Ê+zf£¢·h§~Ûiÿûàz¹\x1e®w¥¢¸?¨èÚ&¢)ߢ^[f
prev parent reply other threads:[~2014-01-14 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 9:01 [PATCH] spi: clps711x: Add MODULE_ALIAS to support module auto-loading Axel Lin
2014-01-14 14:21 ` Mark Brown
[not found] ` <20140114142159.GN15567-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-14 17:22 ` Alexander Shiyan
[not found] ` <1389720129.337538528-tO/HdyGGtlvWO3iv0lnsqw@public.gmane.org>
2014-01-14 17:41 ` Mark Brown
[not found] ` <20140114174100.GS15567-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-14 17:58 ` Alexander Shiyan
[not found] ` <1389722311.613593800-tO/HdyGGtlvWO3iv0lnsqw@public.gmane.org>
2014-01-14 18:00 ` Mark Brown
[not found] ` <20140114180048.GU15567-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-14 18:04 ` Alexander Shiyan [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=1389722667.687082955@f317.i.mail.ru \
--to=shc_work-jgs/udohzui@public.gmane.org \
--cc=axel.lin-8E1dMatC8ynQT0dZR+AlfA@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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