From: Wolfram Sang <wsa@the-dreams.de>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH] i2c: immediately mark ourselves as registered
Date: Mon, 14 Mar 2016 15:58:51 +0100 [thread overview]
Message-ID: <20160314145850.GA15426@katana> (raw)
In-Reply-To: <20160314141903.GB5699@sudip-laptop>
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
> @@ -2128,6 +2130,7 @@ class_err:
> bus_err:
> #endif
> bus_unregister(&i2c_bus_type);
> + is_registered = false;
Right. Fixed up locally, above the bus_unregister though. Thanks!
> Sorry again for the previous patch.
Things happen. Next time, just say it is untested, or better: Test
before sending. I'll pay more attention, too. Case closed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-14 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 9:53 [PATCH] i2c: immediately mark ourselves as registered Wolfram Sang
2016-03-14 14:19 ` Sudip Mukherjee
2016-03-14 14:58 ` Wolfram Sang [this message]
2016-03-14 23:26 ` Nicolai Stange
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=20160314145850.GA15426@katana \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=thierry.reding@gmail.com \
/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).