From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Sachin Kamat <sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Naveen Krishna Chatradhi
<ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH 1/1] i2c: exynos5: Use reinit_completion instead of INIT_COMPLETION
Date: Tue, 5 Nov 2013 11:10:55 +0100 [thread overview]
Message-ID: <20131105101055.GA2660@katana> (raw)
In-Reply-To: <1383643630-5036-1-git-send-email-sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
On Tue, Nov 05, 2013 at 02:57:10PM +0530, Sachin Kamat wrote:
> INIT_COMPLETION was replaced by reinit_completion vide commit 2c9627cca471
> ("tree-wide: use reinit_completion instead of INIT_COMPLETION"). Use it to
> avoid the following build error:
> drivers/i2c/busses/i2c-exynos5.c:538:9: error:
> undefined identifier 'INIT_COMPLETION'
>
> Signed-off-by: Sachin Kamat <sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
You can ignore this topic. akpm (who has the change in his tree) usually
takes care of this.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-05 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 9:27 [PATCH 1/1] i2c: exynos5: Use reinit_completion instead of INIT_COMPLETION Sachin Kamat
[not found] ` <1383643630-5036-1-git-send-email-sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-11-05 9:38 ` Naveen Krishna Ch
2013-11-05 10:10 ` Wolfram Sang [this message]
2013-11-05 10:21 ` Sachin Kamat
[not found] ` <CAK9yfHwv3T6OXO59b+VeFHLU6mxn1Gw+BotOBLUukHuArZ0qig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-05 10:56 ` Wolfram Sang
2013-11-05 11:09 ` Sachin Kamat
[not found] ` <CAK9yfHyf94oTyJRRYtAiaty=AYiPXf+RQTnqdW4-q=zbvwsdtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-05 11:24 ` Wolfram Sang
2013-11-05 11:27 ` Sachin Kamat
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=20131105101055.GA2660@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sachin.kamat-QSEj5FYQhm4dnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.