All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tadeusz Struk <tadeusz.struk@linaro.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Sungjong Seo <sj1557.seo@samsung.com>,
	linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	syzbot+a4087e40b9c13aad7892@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 2/2] exfat: check if cluster num is valid
Date: Mon, 16 May 2022 16:38:59 -0700	[thread overview]
Message-ID: <fe20ae9b-041d-a5eb-d32b-7c79a87e8cf0@linaro.org> (raw)
In-Reply-To: <CAKYAXd_kcZF0tHMX_CsR83qmX25PhdGQPJibMh1-30=5przrjQ@mail.gmail.com>

On 5/16/22 16:31, Namjae Jeon wrote:
>>> Looks good.
>>> And it seems that WARN_ON() is no longer needed.
>> Right. Do you want me to send a follow up patch that drops the WARN_ONs?
> You don't need to do it. I have applied this patch to #exfat dev
> branch after removing it.
> Note that I have combined 1/2 into 2/2 patch.
> Thanks!

That's fine with me. Thanks for taking it.

-- 
Thanks,
Tadeusz

  reply	other threads:[~2022-05-16 23:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220511185940epcas1p3c5eb0603b969fe2753b4f16f6f8842a7@epcas1p3.samsung.com>
2022-05-11 18:59 ` [PATCH v2 1/2] exfat: move is_valid_cluster to a common header Tadeusz Struk
2022-05-11 18:59   ` [PATCH v2 2/2] exfat: check if cluster num is valid Tadeusz Struk
2022-05-15 14:52     ` Sungjong Seo
2022-05-16 14:51       ` Tadeusz Struk
2022-05-16 23:31         ` Namjae Jeon
2022-05-16 23:38           ` Tadeusz Struk [this message]
2022-05-15 14:38   ` [PATCH v2 1/2] exfat: move is_valid_cluster to a common header Sungjong Seo

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=fe20ae9b-041d-a5eb-d32b-7c79a87e8cf0@linaro.org \
    --to=tadeusz.struk@linaro.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj1557.seo@samsung.com \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+a4087e40b9c13aad7892@syzkaller.appspotmail.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 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.