From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/mani/mhi
Date: Wed, 18 Nov 2020 09:51:38 -0000 [thread overview]
Message-ID: <160569309852.19849.9234622621959157276@gitolite.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
---
service: git-receive-pack
repo: pub/scm/linux/kernel/git/mani/mhi
user: mani
changes:
- ref: refs/heads/mhi-next
old: 23d784d48cd094094da0af7111a4cc92136ce3dd
new: 7570a8f9b99aec5d9a82115d1cac327f3827b450
log: revlist-23d784d48cd0-7570a8f9b99a.txt
[-- Attachment #2: revlist-23d784d48cd0-7570a8f9b99a.txt --]
[-- Type: text/plain, Size: 2499 bytes --]
9b627c25e70816a5e1dca940444b5029065b4d60 bus: mhi: core: Remove double locking from mhi_driver_remove()
8ff3f7bdde45b32f9294fc87e4bd76f369178664 bus: mhi: core: fix potential operator-precedence with BHI macros
855a70c12021bdc5df60512f1d3f6d492dc715be bus: mhi: Add MHI PCI support for WWAN modems
f4d0b39c842585c74bce8f8a80553369181b72df bus: mhi: core: Fix null pointer access when parsing MHI configuration
a7f422f2f89e7d48aa66e6488444a4c7f01269d5 bus: mhi: Fix channel close issue on driver remove
56c8ea864018a995c96810c9536d98a879b89218 bus: mhi: core: Remove unnecessary counter from mhi_firmware_copy()
a8ca15a9c73f92703492e8afe25103a34504851b bus: mhi: core: Add missing EXPORT_SYMBOL for mhi_get_mhi_state()
78e1d22687ff1fd320abac12e8a607ea79782c48 bus: mhi: core: Expose mhi_get_exec_env() API for controllers
bca7218099e0796901a9c27366e145d9f485c81a bus: mhi: core: Remove unused mhi_fw_load_worker() declaration
9e1660e5c396ee081907386d0b95b8e0804a6c86 bus: mhi: core: Rename RDDM download function to use proper words
da7bdbf67db232234bb55e083c57b930c2010f95 bus: mhi: core: Skip RDDM download for unknown execution environment
1b55c16a5e4718f58ed58cfdfe37fe4cd4d89f88 bus: mhi: core: Use appropriate names for firmware load functions
8f70397876872789b2a5deba804eb6216fb5deb7 bus: mhi: core: Move to using high priority workqueue
8e0559921f9afc01fe0457c5e136ce4a7ae8f0d3 bus: mhi: core: Skip device wake in error or shutdown states
3fb81a4d5f2f55b1596cb5cffca98c97ca43f07a bus: mhi: core: Move to SYS_ERROR regardless of RDDM capability
0c76b3fa580da8f65333b8774205f0a72ffe844c bus: mhi: core: Prevent sending multiple RDDM entry callbacks
12e050c77be036377fee479dccd479202d8d6853 bus: mhi: core: Move to an error state on any firmware load failure
faa257075bcc35e2c2ee68eb83e4e53d3bb02a90 bus: mhi: core: Use appropriate label in firmware load handler API
dc53d862eab89000ebc87240274943793f0af682 bus: mhi: core: Move to an error state on mission mode failure
40c3127187cb38ed255ba4473e11cd70385c7431 bus: mhi: core: Check for IRQ availability during registration
556bbb442bbb44f429dbaa9f8b48e0b4cda6e088 bus: mhi: core: Separate system error and power down handling
a03c7a86e12721da9f6bb509dddda19fd9ae8c6c bus: mhi: core: Mark and maintain device states early on after power down
6cc1716102b55497dd557e8295a3177315332f9a bus: mhi: core: Remove MHI event ring IRQ handlers when powering down
7570a8f9b99aec5d9a82115d1cac327f3827b450 Merge branch 'mhi-ath11k-immutable' into mhi-next
next reply other threads:[~2020-11-18 9:51 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 9:51 Gitolite [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-27 17:27 post-receive: pub/scm/linux/kernel/git/mani/mhi Gitolite
2021-08-09 10:08 Gitolite
2021-08-09 9:53 Gitolite
2021-07-16 11:56 Gitolite
2021-07-16 11:40 Gitolite
2021-06-25 12:28 Gitolite
2021-06-25 5:32 Gitolite
2021-06-21 15:48 Gitolite
2021-06-21 15:46 Gitolite
2021-06-19 7:55 Gitolite
2021-06-12 7:09 Gitolite
2021-06-12 6:54 Gitolite
2021-06-06 15:27 Gitolite
2021-05-24 4:53 Gitolite
2021-05-24 4:46 Gitolite
2021-05-24 4:42 Gitolite
2021-05-24 4:37 Gitolite
2021-05-24 4:36 Gitolite
2021-05-21 17:07 Gitolite
2021-05-21 11:48 Gitolite
2021-04-11 5:41 Gitolite
2021-04-09 13:19 Gitolite
2021-04-09 4:30 Gitolite
2021-04-08 6:59 Gitolite
2021-04-07 9:07 Gitolite
2021-04-07 8:41 Gitolite
2021-04-07 6:59 Gitolite
2021-03-31 18:42 Gitolite
2021-03-31 11:37 Gitolite
2021-03-16 6:18 Gitolite
2021-03-16 6:08 Gitolite
2021-03-15 5:31 Gitolite
2021-03-10 14:41 Gitolite
2021-02-10 14:29 Gitolite
2021-02-05 12:56 Gitolite
2021-02-05 12:55 Gitolite
2021-02-05 12:52 Gitolite
2021-02-05 12:30 Gitolite
2021-01-27 11:16 Gitolite
2021-01-27 11:16 Gitolite
2021-01-21 11:40 Gitolite
2021-01-21 11:23 Gitolite
2021-01-21 7:53 Gitolite
2021-01-21 7:50 Gitolite
2021-01-21 7:36 Gitolite
2021-01-06 13:19 Gitolite
2021-01-06 13:13 Gitolite
2021-01-05 8:32 Gitolite
2020-12-02 16:36 Gitolite
2020-12-02 9:01 Gitolite
2020-12-01 13:38 Gitolite
2020-11-28 7:13 Gitolite
2020-11-20 6:40 Gitolite
2020-11-20 6:25 Gitolite
2020-11-18 9:46 Gitolite
2020-11-18 9:36 Gitolite
2020-11-18 9:29 Gitolite
2020-11-18 9:18 Gitolite
2020-11-18 8:54 Gitolite
2020-11-16 6:38 Gitolite
2020-11-16 5:09 Gitolite
2020-11-16 3:02 Gitolite
2020-11-09 13:28 Gitolite
2020-11-09 12:04 Gitolite
2020-11-09 11:57 Gitolite
2020-10-30 7:40 Gitolite
2020-09-29 15:40 Gitolite
2020-09-28 4:12 Gitolite
2020-09-27 3:38 Gitolite
2020-09-21 15:46 Gitolite
2020-09-15 8:22 Gitolite
2020-09-15 8:19 Gitolite
2020-08-19 4:02 Gitolite
2020-08-18 5:47 Gitolite
2020-07-23 14:22 Gitolite
2020-07-16 3:10 Gitolite
2020-06-19 7:47 Gitolite
2020-05-14 5:44 Gitolite
2020-05-13 10:35 Gitolite
2020-05-09 8:28 Gitolite
2020-04-30 19:33 Gitolite
2020-04-13 6:56 Gitolite
2020-02-04 8:37 Gitolite
2020-01-31 13:54 Gitolite
2020-01-31 13:54 Gitolite
2020-01-31 2:48 Gitolite
2020-01-31 2:41 Gitolite
2020-01-30 16:16 Gitolite
2020-01-30 4:18 Gitolite
2020-01-30 3:46 Gitolite
2020-01-29 13:25 Gitolite
2020-01-29 12:31 Gitolite
2020-01-29 5:06 Gitolite
2020-01-27 14:33 Gitolite
2020-01-23 10:58 Gitolite
2020-01-23 10:19 Gitolite
2020-01-23 9:26 Gitolite
2020-01-22 5:18 Gitolite
2020-01-22 4:28 Gitolite
2020-01-21 18:08 Gitolite
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=160569309852.19849.9234622621959157276@gitolite.kernel.org \
--to=devnull@kernel.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.