From: Richard Weinberger <richard.weinberger@gmail.com>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>,
"richard@nod.at" <richard@nod.at>
Subject: Re: [PATCH] Remove __work from PIPELINE_INBAND_WORK_INITIALIZER
Date: Thu, 7 Apr 2022 10:04:24 +0200 [thread overview]
Message-ID: <CAFLxGvwpPFtdxjBrQ4cEpbniHTX9YmZ-pmWCtR2ZOutPuD82HQ@mail.gmail.com> (raw)
In-Reply-To: <6fabb15e3e078aae8bc23d1b4970f484e03e9943.camel@siemens.com>
On Thu, Apr 7, 2022 at 10:03 AM Bezdeka, Florian via Xenomai
<xenomai@xenomai.org> wrote:
>
> Hi Richard,
>
> On Wed, 2022-04-06 at 23:06 +0200, Richard Weinberger via Xenomai
> wrote:
> > ipipe took a copy of the queued work, __work was used to determine how much
> > bytes had to get copied.
> > With dovetail no copy as taken and the __work parameter is no longer
> ^^ is
> > useful, so we can get rid of it.
>
> The rest LGTM. Commit message could be fixed up on merge as long as Jan
> does not insist on sending out a v2.
I'll happily send a v2. :-)
--
Thanks,
//richard
next prev parent reply other threads:[~2022-04-07 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 21:06 [PATCH] Remove __work from PIPELINE_INBAND_WORK_INITIALIZER Richard Weinberger
2022-04-07 8:03 ` Bezdeka, Florian
2022-04-07 8:04 ` Richard Weinberger [this message]
2022-04-07 9:35 ` Jan Kiszka
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=CAFLxGvwpPFtdxjBrQ4cEpbniHTX9YmZ-pmWCtR2ZOutPuD82HQ@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=florian.bezdeka@siemens.com \
--cc=richard@nod.at \
--cc=xenomai@xenomai.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.