From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PULL REQUEST] i2c-mux for 4.12-rc2
Date: Tue, 16 May 2017 19:06:29 +0200 [thread overview]
Message-ID: <20170516170629.gn55etnp3pdoyfg4@ninjato> (raw)
In-Reply-To: <2ee240a4-6031-3d80-f850-daff4b0182bf@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
On Mon, May 15, 2017 at 06:56:07PM +0200, Peter Rosin wrote:
> Wolfram,
>
> This fixes an old bug in resource cleanup on failure in i2c-mux-reg and a
> new log spamming bug from this merge window in the i2c-mux core.
>
> Please pull.
>
> Cheers,
> peda
>
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
> https://github.com/peda-r/i2c-mux.git i2c-mux/for-current
>
> for you to fetch changes up to 9fce894d03a98ec8e8e8106a964644633d2772ee:
>
> i2c: mux: only print failure message on error (2017-05-15 18:49:11 +0200)
>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-05-16 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 16:56 [PULL REQUEST] i2c-mux for 4.12-rc2 Peter Rosin
2017-05-16 17:06 ` Wolfram Sang [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=20170516170629.gn55etnp3pdoyfg4@ninjato \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
/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