Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "FRÉDÉRIC RECOULES" <frederic.recoules@univ-grenoble-alpes.fr>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	frederic recoules <frederic.recoules@orange.fr>
Subject: Re: [PATCH] [inline assembly] fix pcm_dmix_i386.h assembly chunk interfaces
Date: Tue, 05 May 2020 15:52:19 +0200	[thread overview]
Message-ID: <s5heerybib0.wl-tiwai@suse.de> (raw)
In-Reply-To: <771384288.121039.1588620316734.JavaMail.zimbra@univ-grenoble-alpes.fr>

On Mon, 04 May 2020 21:25:16 +0200,
FRÉDÉRIC RECOULES wrote:
> 
> Hi Takashi,
> 
> I would like an update on the review process ([PATCH */6 V2] [pcm_dmix
> assembly])
> 
> As a reminder, I split the changes in 6 distinct patches.
> The 3 first patches produce exactly the same binary output, so they do not
> need testing.
> The 4th one has just some minor change due to the fact that I added an
> instruction -- I am highly confident it breaks nothing.

The compile tests passed with a few different compiler set, so that's
good.  But there were some issues with the patch format.  IIRC, the
patch 2 couldn't be applied to the latest git tree cleanly (some space
letter issues?), so I had to manually modify it.

Also, some style issues:

- Please avoid a prefix like "[configure]" in the subject.
  The prefix with "[PATCH xxx]" is good, and this should remain, but
  the next prefix should be "configure:" instead.  Otherwise the
  prefix with the brackets are pruned at applying a patch via git-am.

- Please give more texts about why the change is done.
  In all your patches, there are no explanations why you change it.
  It's often more important than describing what you're changing.
  For example, the patch 2 "change the token by symbolic names".  Why
  is this needed to be symbolic names?  Write some more information in
  each patch description.

- We usually use #ifdef without space between "#" and "ifdef".
  Let's keep that style consistently.

> If you need I test the 2 last ones (that reduce the size of the produced
> binary), could you point me out what test I should run?

We need at least some build tests with different compiler versions and
check whether dmix actually works (not necessarily on all of them but
some of those compiled results).

> Meanwhile, my deadline comes and I would really appreciate to see the patches
> applied by wednesday night.

If you can work on the above and resubmit v3 patchset, I'll happily
apply them.


Thanks!

Takashi

  reply	other threads:[~2020-05-05 13:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 16:57 [PATCH] [inline assembly] fix pcm_dmix_i386.h assembly chunk interfaces frederic.recoules
2020-04-29  8:19 ` Takashi Iwai
2020-04-30  9:41   ` FRÉDÉRIC RECOULES
2020-05-04 19:25     ` FRÉDÉRIC RECOULES
2020-05-05 13:52       ` Takashi Iwai [this message]
2020-05-06 18:07         ` FRÉDÉRIC RECOULES
  -- strict thread matches above, loose matches on Subject: below --
2020-04-27  7:36 frederic.recoules
2020-04-27 13:47 ` Takashi Iwai
     [not found]   ` <1871992915.6898305.1587998132827.JavaMail.zimbra@univ-grenoble-alpes.fr>
2020-04-27 15:12     ` Takashi Iwai
2020-04-27 16:00       ` FRÉDÉRIC RECOULES

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=s5heerybib0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=frederic.recoules@orange.fr \
    --cc=frederic.recoules@univ-grenoble-alpes.fr \
    /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