public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ferdinand Blomqvist <ferdinand.blomqvist@gmail.com>
To: Aiden Leong <aiden.leong@aibsd.com>
Cc: Kees Cook <keescook@chromium.org>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	YueHaibing <yuehaibing@huawei.com>,
	dm-devel <dm-devel@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>,
	Anton Vorontsov <anton@enomsg.org>,
	Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>
Subject: Re: [RFC] Reed-Solomon Code: Update no_eras to the actual number of errors
Date: Thu, 25 Jun 2020 16:15:17 +0300	[thread overview]
Message-ID: <20200625131517.GD1036@mail-personal> (raw)
In-Reply-To: <5f4008d5-1ddd-443e-9190-a8565746698d.aiden.leong@aibsd.com>

Hi, 

On 2020-06-25 14:46:11, Aiden Leong wrote:
>
>BTW: I do believe these functions should be split into a function family. It's really hard to call them correctly and hard to debug as well.

I don't think the functions should be split up. Most probably it is the
documentation that should be improved :) But, I do agree that it is not
that easy to call the functions correctly.

Best,
Ferdinand

-- 
Ferdinand Blomqvist
ferdinand.blomqvist[at]gmail.com
GPG key: 9EFB 7A2C 0432 4EC5 32BA FA61 CFE9 4164 93E8 B9E4

      parent reply	other threads:[~2020-06-25 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25  4:10 [RFC] Reed-Solomon Code: Update no_eras to the actual number of errors Aiden Leong
2020-06-25  5:35 ` Kees Cook
2020-06-25  5:50   ` Joe Perches
     [not found]   ` <5f4008d5-1ddd-443e-9190-a8565746698d.aiden.leong@aibsd.com>
2020-06-25 13:15     ` Ferdinand Blomqvist [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=20200625131517.GD1036@mail-personal \
    --to=ferdinand.blomqvist@gmail.com \
    --cc=agk@redhat.com \
    --cc=aiden.leong@aibsd.com \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=dm-devel@redhat.com \
    --cc=gustavo@embeddedor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=yuehaibing@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox