From: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
To: "greg kh" <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Re: how to determine whether the source code is same between two kernels
Date: Wed, 8 May 2019 17:43:02 +0800 (GMT+08:00) [thread overview]
Message-ID: <426d5d69.72741.16a96d32c0a.Coremail.wuzhouhui14@mails.ucas.ac.cn> (raw)
In-Reply-To: <20190508092554.GC2361@kroah.com>
> -----Original Messages-----
> From: "Greg KH" <greg@kroah.com>
> Sent Time: 2019-05-08 17:25:54 (Wednesday)
> To: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
> Cc: kernelnewbies@kernelnewbies.org
> Subject: Re: how to determine whether the source code is same between two kernels
>
> On Wed, May 08, 2019 at 04:52:46PM +0800, wuzhouhui wrote:
> > Hi,
> >
> > Suppose I have two kernels, one is A.B.C build by people Tom. And
> > the other is A.B.C build by Jerry. The source code have been deleted
> > after kernel is build and installed. Now I want to know whether the
> > source code of these two kernel is the same (even if they have the same
> > name). All I have is binaries (e.g. vmlinux, config, *.ko, System.map).
^^^^^^^
vmlinuz, sorry for the typo.
> > Is it possible?
Using word "same" is too strict. At least, I want to know the source code of
two kernels is "equivalent". I already know that the source code is equivalent
if the srcversion of two modules is same (correct me if it is wrong). Does
vmlinuz has srcversion too?
>
> Maybe, but not very easily.
>
> Good luck!
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-05-08 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:52 how to determine whether the source code is same between two kernels wuzhouhui
2019-05-08 9:25 ` Greg KH
2019-05-08 9:43 ` wuzhouhui [this message]
2019-05-08 10:08 ` greg kh
2019-05-08 13:43 ` Valdis Klētnieks
2019-05-11 2:11 ` Aruna Hewapathirane
2019-05-11 3:58 ` Valdis Klētnieks
2019-05-11 13:20 ` Aruna Hewapathirane
2019-05-11 13:53 ` Valdis Klētnieks
2019-05-11 23:47 ` chiachen
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=426d5d69.72741.16a96d32c0a.Coremail.wuzhouhui14@mails.ucas.ac.cn \
--to=wuzhouhui14@mails.ucas.ac.cn \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.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).