From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
konrad.wilk@oracle.com, tiwai@suse.de
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, jgross@suse.com
Subject: Re: [PATCH 0/5] for-linux/sndif: add explicit back and front synchronization
Date: Thu, 12 Apr 2018 20:13:02 +0300 [thread overview]
Message-ID: <eb882793-4024-7299-9d34-62d3cf462a33@gmail.com> (raw)
In-Reply-To: <690a322e-20a6-fe55-1d87-0a52de126ee0@oracle.com>
On 04/12/2018 08:13 PM, Boris Ostrovsky wrote:
> On 04/12/2018 12:55 PM, Oleksandr Andrushchenko wrote:
>> On 04/12/2018 07:55 PM, Boris Ostrovsky wrote:
>>> On 04/12/2018 12:11 PM, Oleksandr Andrushchenko wrote:
>>>> Hello, Konrad, Takashi!
>>>>
>>>> Could you please review the *Linux Kernel* version of the changes?
>>>> As I said in the cover letter below there is no functional changes
>>>> comparing to the corresponding Xen version, but spaces to tabs.
>>>> Still, formally, I have to drop the R-b tags and request for the new
>>>> review.
>>> Is there any reason why this all can't be done in a single patch?
>> Just to preserve the history of the changes?
> The history is tracked in Xen tree and since you are only updating the
> header file I don't think we gain much by repeating it here.
makes sense
>>> This is just syncing up with the canonical definition in Xen.
>> Do you want me to squash and resend?
>
> Yes, please.
will do
> -boris
prev parent reply other threads:[~2018-04-12 17:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 16:00 Oleksandr Andrushchenko
2018-04-12 16:00 ` [PATCH 1/5] xen/sndif: Introduce protocol version Oleksandr Andrushchenko
2018-04-12 16:00 ` [PATCH 2/5] xen/sndif: Fix missed "reserved" fields in comments Oleksandr Andrushchenko
2018-04-12 16:01 ` [PATCH 3/5] xen/sndif: Make requests and responses 64 octets long Oleksandr Andrushchenko
2018-04-12 16:01 ` [PATCH 4/5] xen/sndif: Add explicit back and front synchronization Oleksandr Andrushchenko
2018-04-12 16:01 ` [PATCH 5/5] xen/sndif: Add explicit back and front parameter negotiation Oleksandr Andrushchenko
2018-04-12 16:11 ` [PATCH 0/5] for-linux/sndif: add explicit back and front synchronization Oleksandr Andrushchenko
2018-04-12 16:55 ` Boris Ostrovsky
2018-04-12 16:55 ` Oleksandr Andrushchenko
2018-04-12 17:13 ` Boris Ostrovsky
2018-04-12 17:13 ` Oleksandr Andrushchenko [this message]
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=eb882793-4024-7299-9d34-62d3cf462a33@gmail.com \
--to=andr2000@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=tiwai@suse.de \
--cc=xen-devel@lists.xenproject.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®