From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 4/6] api/channel: Add channel abstraction for message passing
Date: Fri, 30 Sep 2022 11:17:56 +0200 [thread overview]
Message-ID: <Yza0ROA7bfttCnAD@pevik> (raw)
In-Reply-To: <20220927161408.23743-5-rpalethorpe@suse.com>
Hi Richie,
...
> diff --git a/lib/tst_channel.c b/lib/tst_channel.c
...
> +static void pipe_chan_send(struct tst_chan *self)
> +{
> + struct tst_pchan *priv = self->priv;
> + const enum tst_pchan_state state =
> + TST_STATE_GET(&priv->mach, 1 << PCS_IDLE | 1 << PCS_SEND_DATA | 1 << PCS_RECV_ACK);
> +
> + TST_STATE_EXP(&self->mach, 1 << CHS_READY | 1 << CHS_SEND);
nit: git am complains:
Applying: api/channel: Add channel abstraction for message passing
.git/rebase-apply/patch:293: space before tab in indent.
TST_STATE_EXP(&self->mach, 1 << CHS_READY | 1 << CHS_SEND);
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-30 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 16:14 [LTP] [PATCH 0/6] Locally distributed work API Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 1/6] api/epoll: Add safe epoll functions Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 2/6] api/evloop: Add helpers for creating an event loop Richard Palethorpe via ltp
2022-09-30 13:36 ` Petr Vorel
2022-09-27 16:14 ` [LTP] [PATCH 3/6] api/state_machine: Add validating state machines Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 4/6] api/channel: Add channel abstraction for message passing Richard Palethorpe via ltp
2022-09-30 9:17 ` Petr Vorel [this message]
2022-09-27 16:14 ` [LTP] [PATCH 5/6] api/worker: Add library for distributing work over multiple procs Richard Palethorpe via ltp
2022-09-27 16:14 ` [LTP] [PATCH 6/6] read_all: Migrate to the worker lib Richard Palethorpe via ltp
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=Yza0ROA7bfttCnAD@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.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 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.