All of lore.kernel.org
 help / color / mirror / Atom feed
From: brutallesale@gmail.com (Bogicevic Sasa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: objdiff usage
Date: Wed, 2 Dec 2015 11:07:21 +0100	[thread overview]
Message-ID: <20151202100721.GC3282@gmail.com> (raw)
In-Reply-To: <CAOmT4fTqYq2n9oJKi_fr1naeUo-Z=-T6J6Srdk9dTg_W16exPg@mail.gmail.com>

On 12/02/2015, bojan prtvar wrote:
>Hi Sasa,
>
>On Wed, Dec 2, 2015 at 9:56 AM, Bogicevic Sasa <brutallesale@gmail.com> wrote:
>> Hi all,
>> I am looking for a guidance on ./scripts/objdiff usage, cant seem to
>> find a goot example of the scenario where you for example make a bunch of
>> changes (code style issues) in one folder and need to check if that?changes
>> don't change the object file. That can speed up code cleaning quite a bi but
>> all I found online are patches related to objdiff.
>>                             ?
>> Thanks,Sasa
>>
>
>
>Example usage link can be fund in the objdiff commit thread:
>https://lkml.org/lkml/2014/4/7/312
>
>Regards,
>Bojan
Hvala Bojane :)
Thanks Bojan,
What about the case where you dont have object files to compare ?
For example driver/pci/hotplug in my case ? How do you prove that your
changes didn't brake something ?

Thanks, Sasa
{
	name: Sasa Bogicevic
	phone: +381:606006200
}

  reply	other threads:[~2015-12-02 10:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  8:56 objdiff usage Bogicevic Sasa
2015-12-02  9:57 ` bojan prtvar
2015-12-02 10:07   ` Bogicevic Sasa [this message]
2015-12-02 10:31     ` bojan prtvar
2015-12-02 10:39       ` Bogicevic Sasa
2015-12-02 10:56         ` bojan prtvar
2015-12-02 11:13           ` Bogicevic Sasa

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=20151202100721.GC3282@gmail.com \
    --to=brutallesale@gmail.com \
    --cc=kernelnewbies@lists.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 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.