From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Rosin <peda@axentia.se>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PULL REQUEST] i2c for 5.10
Date: Sun, 25 Oct 2020 13:37:45 +0100 [thread overview]
Message-ID: <20201025123745.GA7614@kunai> (raw)
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Linus,
I2C has a regression fix which should go into rc1 and to stable kernels
as well.
Please pull.
Thanks,
Wolfram
The following changes since commit d76913908102044f14381df865bb74df17a538cb:
Merge tag 'block-5.10-2020-10-24' of git://git.kernel.dk/linux-block (2020-10-24 12:46:42 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-5.10
for you to fetch changes up to 8058d69905058ec8f467a120b5ec5bb831ea67f3:
i2c: core: Restore acpi_walk_dep_device_list() getting called after registering the ACPI i2c devs (2020-10-25 13:33:54 +0100)
----------------------------------------------------------------
Hans de Goede (1):
i2c: core: Restore acpi_walk_dep_device_list() getting called after registering the ACPI i2c devs
drivers/i2c/i2c-core-acpi.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-10-25 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 12:37 Wolfram Sang [this message]
2020-10-25 18:35 ` [PULL REQUEST] i2c for 5.10 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-12-12 18:30 Wolfram Sang
2020-12-12 21:03 ` pr-tracker-bot
2020-12-05 22:11 Wolfram Sang
2020-12-05 23:33 ` pr-tracker-bot
2020-11-07 18:39 Wolfram Sang
2020-11-07 19:43 ` pr-tracker-bot
2020-10-21 6:55 Wolfram Sang
2020-10-21 18:35 ` pr-tracker-bot
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=20201025123745.GA7614@kunai \
--to=wsa@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=torvalds@linux-foundation.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.