From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
alsa-devel@alsa-project.org, xen-devel@lists.xen.org,
linux-kernel@vger.kernel.org
Cc: tiwai@suse.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH RESEND 00/11] ALSA: vsnd: Add Xen para-virtualized frontend driver
Date: Mon, 7 Aug 2017 15:33:24 +0300 [thread overview]
Message-ID: <2b1fea9d-3c5c-bfc7-24f6-6d4bcc691357@gmail.com> (raw)
In-Reply-To: <46d253b3-abe3-e2f4-f787-38a600bd5214@sakamocchi.jp>
On 08/07/2017 03:30 PM, Takashi Sakamoto wrote:
> On Aug 7 2017 21:18, Oleksandr Andrushchenko wrote:
>>> Your first patch includes code difference under line 26, thus it
>>> expects existence of a file 'sound/drivers/xen-front.c' in tree.
>>> However, the file is not introduced in any upstream yet; at least,
>>> Linus's tree and Iwai-san's tree.
>> I missed the very first patch in the series, this is why, my bad
>
> When I did the same mistake, I take git-hash for a first commit in
> series as an argument into git-format-patch command. But this
> operation generated patchset which starts at second commit. I solved
> this to add '~', like.
>
> $ git format-patch -s the-git-hash~...
>
> Or pick up the hash for a commit just before a first commit in the
> series. For your information ;)
>
thank you for the hint, will use instead of specifying number of patches
(this is why I missed one and made so much noise)
>
> Regards
>
> Takashi Sakamoto
Thank you,
Oleksandr
prev parent reply other threads:[~2017-08-07 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 11:50 [PATCH RESEND 00/11] ALSA: vsnd: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 01/11] ALSA: vsnd: Implement driver's probe/remove Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 02/11] ALSA: vsnd: Implement Xen bus state handling Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 03/11] ALSA: vsnd: Read sound driver configuration from Xen store Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 04/11] ALSA: vsnd: Implement Xen event channel handling Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 05/11] ALSA: vsnd: Implement handling of shared buffers Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 06/11] ALSA: vsnd: Introduce ALSA virtual sound driver Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 07/11] ALSA: vsnd: Initialize virtul sound card Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 08/11] ALSA: vsnd: Add timer for period interrupt emulation Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 09/11] ALSA: vsnd: Implement ALSA PCM operations Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 10/11] ALSA: vsnd: Implement communication with backend Oleksandr Andrushchenko
2017-08-07 11:50 ` [PATCH RESEND 11/11] ALSA: vsnd: Introduce Kconfig option to enable Xen PV sound Oleksandr Andrushchenko
2017-08-07 12:09 ` [PATCH RESEND 00/11] ALSA: vsnd: Add Xen para-virtualized frontend driver Takashi Sakamoto
2017-08-07 12:18 ` Oleksandr Andrushchenko
2017-08-07 12:30 ` Takashi Sakamoto
2017-08-07 12:33 ` 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=2b1fea9d-3c5c-bfc7-24f6-6d4bcc691357@gmail.com \
--to=andr2000@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=oleksandr_andrushchenko@epam.com \
--cc=tiwai@suse.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).