All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilbert Adikankwu <gilbertadikankwu@gmail.com>
To: andi.shyti@kernel.org
Cc: andi.shyti@intel.com, outreachy@lists.linux.dev, Julia.Lawall@inria.fr
Subject: [Outreachy Applicant] NEEDS SOME CLARIFICATIONS
Date: Tue, 10 Oct 2023 05:20:33 +0100	[thread overview]
Message-ID: <ZSTRETv7sO+1A6/G@gilbert-PC> (raw)

Hello Andi and Julia,

Thank you so much for your responses.

I need some help with moving forward in the tutorial.

I am at the "Make a driver change" step of the first patch tutorial. The tutorial made the look like finding the _main.c file of the driver and locating its probe function was quite easy.

I ran lsmod as instructed and picked e1000e. I used git grep e1000e -- '*Makefile' to search for its subdirectory in the kernel tree. This is where it got tricky for me, I thought I would find a .c file like e1000e.c or e1000e_main.c as was shown in the VM example(I'm using native Linux) but I can see in the subdirectory are .o files that I can't modify. And I don't what to do or how to find the probe function I'm supposed to modify

I tried the above process for a couple more names in the list returned by lsmod and it is the same issue.

Please advise

Thanks
Gilbert


             reply	other threads:[~2023-10-10  4:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  4:20 Gilbert Adikankwu [this message]
2023-10-10  6:20 ` [Outreachy Applicant] NEEDS SOME CLARIFICATIONS Deepak R Varma
2023-10-10  7:15 ` Andi Shyti
     [not found]   ` <CAKrXSsZe4w-K7kzGu=8_R_h1TSVtJWL1_TmFX-S-A1jCrPeCrg@mail.gmail.com>
2023-10-10 16:36     ` Julia Lawall
2023-10-10 16:42       ` Gilbert Adikankwu
2023-10-10 16:43       ` Andi Shyti
2023-10-10 16:45         ` Gilbert Adikankwu
2023-10-10 17:03           ` Andi Shyti
2023-10-10 17:34             ` Gilbert Adikankwu
2023-10-10 20:54               ` Andi Shyti
2023-10-11  6:15                 ` Gilbert Adikankwu
2023-10-11  6:26                   ` Julia Lawall
2023-10-11  6:37                     ` Gilbert Adikankwu
2023-10-11  7:10                     ` Andi Shyti
2023-10-13  7:59                       ` Gilbert Adikankwu
2023-10-13  8:17                         ` Julia Lawall
  -- strict thread matches above, loose matches on Subject: below --
2023-10-10  6:59 Gilbert Adikankwu
2023-10-10  7:06 Gilbert Adikankwu

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=ZSTRETv7sO+1A6/G@gilbert-PC \
    --to=gilbertadikankwu@gmail.com \
    --cc=20231008212812.tw674m2hbhpyhi5v@zenone.zhora.eu \
    --cc=Julia.Lawall@inria.fr \
    --cc=andi.shyti@intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=outreachy@lists.linux.dev \
    /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.