From: Tetsuhiro Kohada <kohada.t2@gmail.com>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: kohada.tetsuhiro@dc.mitsubishielectric.co.jp,
mori.takahiro@ab.mitsubishielectric.co.jp,
motai.hirotaka@aj.mitsubishielectric.co.jp,
'Sungjong Seo' <sj1557.seo@samsung.com>,
'Namjae Jeon' <linkinjeon@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] exfat: standardize checksum calculation
Date: Thu, 28 May 2020 19:09:04 +0900 [thread overview]
Message-ID: <780793fc-029a-28a6-5970-c21ffc91268b@gmail.com> (raw)
In-Reply-To: <015401d634ad$4628e4c0$d27aae40$@samsung.com>
>> I'll repost the patch, based on the dir-cache patched dev-tree.
>> If dir-cache patch will merge into dev-tree, should I wait until then?
> I will apply them after testing at once if you send updated 5 patches again.
I resend patches for boot_sector.
However, the dir-cache patch hasn't changed, so I haven't reposted it.
BR
next prev parent reply other threads:[~2020-05-28 10:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200525115110epcas1p491bfb477b12825536e81e376f34c7a02@epcas1p4.samsung.com>
2020-05-25 11:50 ` [PATCH 1/4] exfat: redefine PBR as boot_sector Tetsuhiro Kohada
2020-05-25 11:50 ` [PATCH 2/4] exfat: separate the boot sector analysis Tetsuhiro Kohada
2020-05-25 11:50 ` [PATCH 3/4] exfat: add boot region verification Tetsuhiro Kohada
2020-05-26 7:23 ` Namjae Jeon
2020-05-29 16:51 ` kbuild test robot
2020-05-25 11:50 ` [PATCH 4/4] exfat: standardize checksum calculation Tetsuhiro Kohada
2020-05-26 7:32 ` Namjae Jeon
2020-05-27 7:39 ` Tetsuhiro Kohada
2020-05-27 11:28 ` Namjae Jeon
2020-05-28 2:00 ` Tetsuhiro Kohada
2020-05-28 5:03 ` Namjae Jeon
2020-05-28 10:09 ` Tetsuhiro Kohada [this message]
2020-05-28 11:30 ` Namjae Jeon
2020-05-28 5:31 ` [PATCH 1/4] exfat: redefine PBR as boot_sector Sungjong Seo
2020-05-28 12:27 ` Tetsuhiro Kohada
2020-05-29 5:28 ` Sungjong Seo
2020-05-29 6:32 ` Tetsuhiro Kohada
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=780793fc-029a-28a6-5970-c21ffc91268b@gmail.com \
--to=kohada.t2@gmail.com \
--cc=kohada.tetsuhiro@dc.mitsubishielectric.co.jp \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mori.takahiro@ab.mitsubishielectric.co.jp \
--cc=motai.hirotaka@aj.mitsubishielectric.co.jp \
--cc=namjae.jeon@samsung.com \
--cc=sj1557.seo@samsung.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
all inboxes | Powered by JetHome®