From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Hauke Mehrtens <hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hauke.mehrtens-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
thomas.langer-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org
Subject: Re: [PATCH] SPI: make falcon-spi bool
Date: Wed, 4 Jan 2017 10:46:24 +0000 [thread overview]
Message-ID: <20170104104624.z4ijsadskpmd26p5@sirena.org.uk> (raw)
In-Reply-To: <20170103170427.26120-1-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
On Tue, Jan 03, 2017 at 06:04:27PM +0100, Hauke Mehrtens wrote:
> Falcon spi accesses some ebu functions which are not exported and can
> not be accessed when build as module. Make this module bool instead.
Why is the fix here not to export these functions (or longer term to fix
things so that we're not going through custom APIs)?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-01-04 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 17:04 [PATCH] SPI: make falcon-spi bool Hauke Mehrtens
[not found] ` <20170103170427.26120-1-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2017-01-03 18:52 ` Langer, Thomas
2017-01-04 10:46 ` Mark Brown [this message]
[not found] ` <20170104104624.z4ijsadskpmd26p5-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-01-09 23:32 ` Hauke Mehrtens
2017-01-10 12:26 ` Mark Brown
2017-01-10 12:27 ` Applied "spi: make falcon-spi bool" to the spi tree Mark Brown
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=20170104104624.z4ijsadskpmd26p5@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org \
--cc=hauke.mehrtens-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thomas.langer-ral2JQCrhuEAvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).