From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, keescook@chromium.org,
linux-kernel@vger.kernel.org
Cc: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
Subject: [PATCH 0/2] Convert greybus loopback to core async API
Date: Sun, 5 Nov 2017 03:27:37 +0000 [thread overview]
Message-ID: <1509852459-5847-1-git-send-email-pure.logic@nexus-software.ie> (raw)
dbec27298b0d ('staging: greybus: operation: add generic timeout support')
gives the ability to remove lots of the asynchronous operation code in
loopback.
Kees is also doing a cleanup of timer code which for loopback will go away
when converting to the core API.
These two patches kill two birds with err, two stones (no aggression to
birds intended) namely:
- Converting over to the core asynchronous API
- Getting rid of the timer code in loopback which will unblock what Kees is
doing.
Bryan O'Donoghue (2):
staging: greybus: operation: add private data with get/set accessors
staging: greybus: loopback: convert loopback to use generic async
operations
drivers/staging/greybus/loopback.c | 165 +++++++-----------------------------
drivers/staging/greybus/operation.h | 13 +++
2 files changed, 44 insertions(+), 134 deletions(-)
--
2.7.4
next reply other threads:[~2017-11-05 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 3:27 Bryan O'Donoghue [this message]
2017-11-05 3:27 ` [PATCH 1/2] staging: greybus: operation: add private data with get/set accessors Bryan O'Donoghue
2017-11-05 12:19 ` Johan Hovold
2017-11-05 3:27 ` [PATCH 2/2] staging: greybus: loopback: convert loopback to use generic async operations Bryan O'Donoghue
2017-11-05 12:24 ` Johan Hovold
2017-11-06 0:05 ` Bryan O'Donoghue
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=1509852459-5847-1-git-send-email-pure.logic@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®