From: "tiantao (H)" <tiantao6@huawei.com>
To: Wolfram Sang <wsa@kernel.org>
Cc: Tian Tao <tiantao6@hisilicon.com>, <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH drivers/i2c 1/3] i2c: amd8111: Fix coding style issues
Date: Wed, 14 Apr 2021 16:40:01 +0800 [thread overview]
Message-ID: <0e864e39-9755-7fe6-b69d-2d42111d6be1@huawei.com> (raw)
In-Reply-To: <20210414083124.GL2180@ninjato>
在 2021/4/14 16:31, Wolfram Sang 写道:
>>> Is the binary after the patch applied equal to the binary before your
>>> patch? Same question for patch 2.
>> The MD5 value of binary is the same before and after the patch is
>> merged，the log is as below：
> Thanks for checking! What about patch 2?
The MD5 value of binary is the same before and after the patch2 is
merged，the log is as below：
tiantao@ubuntu:~/mailline/linux-next$ make modules M=drivers/i2c/busses/
CC [M] drivers/i2c/busses//i2c-iop3xx.o
MODPOST drivers/i2c/busses//Module.symvers
CC [M] drivers/i2c/busses//i2c-iop3xx.mod.o
LD [M] drivers/i2c/busses//i2c-iop3xx.ko
tiantao@ubuntu:~/mailline/linux-next$ md5sum
drivers/i2c/busses//i2c-iop3xx.o
6c1b7bdd1fa8bb372eee04344e496617 drivers/i2c/busses//i2c-iop3xx.o
tiantao@ubuntu:~/mailline/linux-next$ git am
/home/tiantao/patchi3c/0002-i2c-iop3xx-Fix-coding-style-issues.patch
Applying: i2c: iop3xx: Fix coding style issues
tiantao@ubuntu:~/mailline/linux-next$ make modules M=drivers/i2c/busses/
CC [M] drivers/i2c/busses//i2c-iop3xx.o
MODPOST drivers/i2c/busses//Module.symvers
LD [M] drivers/i2c/busses//i2c-iop3xx.ko
tiantao@ubuntu:~/mailline/linux-next$ md5sum
drivers/i2c/busses//i2c-iop3xx.o
6c1b7bdd1fa8bb372eee04344e496617 drivers/i2c/busses//i2c-iop3xx.o
>
next prev parent reply other threads:[~2021-04-14 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 9:03 [PATCH drivers/i2c 0/3] Fix ERRORs reported by checkpatch Tian Tao
2021-04-05 9:03 ` [PATCH drivers/i2c 1/3] i2c: amd8111: Fix coding style issues Tian Tao
2021-04-13 20:25 ` Wolfram Sang
2021-04-14 1:03 ` tiantao (H)
2021-04-14 8:31 ` Wolfram Sang
2021-04-14 8:40 ` tiantao (H) [this message]
2021-04-15 20:26 ` Wolfram Sang
2021-04-05 9:03 ` [PATCH drivers/i2c 2/3] i2c: iop3xx: " Tian Tao
2021-04-15 20:27 ` Wolfram Sang
2021-04-05 9:03 ` [PATCH drivers/i2c 3/3] i2c: nomadik: Fix space errors Tian Tao
2021-04-15 20:27 ` Wolfram Sang
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=0e864e39-9755-7fe6-b69d-2d42111d6be1@huawei.com \
--to=tiantao6@huawei.com \
--cc=linux-i2c@vger.kernel.org \
--cc=tiantao6@hisilicon.com \
--cc=wsa@kernel.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).