public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: courage angeh <courageangeh@gmail.com>
Cc: outreachy-kernel@googlegroups.com, linux-newbie@vger.kernel.org
Subject: Re: [Outreachy kernel] commiting the .git/hooks/pre-commit and testing the changes on the updated e1000_main.c
Date: Tue, 26 Jul 2016 12:46:14 -0700	[thread overview]
Message-ID: <20160726194613.GA14874@d830.WORKGROUP> (raw)
In-Reply-To: <64c3385b-6ee7-44ac-bb17-e265d5f9ade8@googlegroups.com>

Hi Courage ? ;)
I'll help you.  I'm an outreachy intern now. 

We need to move this thread over to linux-newbie mailing list, since
this outreachy list won't be active until the next application round.
Please 'cc linux-newbie on posts as I've done above.

See comments in line below.
alisons


On Tue, Jul 26, 2016 at 11:06:10AM -0700, courage angeh wrote:
> I am a newbie... just start recently preparing for the out reach program in 
> December.... i started at: https://kernelnewbies.org/Outreachyfirstpatch 
> but i have a number of difficulties:
> 1. After editx... ,  recompiling my driver, installing the changes and 
> rebooting my linux system . I tested the changes but i didn't find the 
> message " I can modify the Linux kernel!".... i contacted the irc 
> channel:#kernel-outreachy but i seemed not to exist.

Let's go step by step. 

Let's make sure you put in a printk that will get printed.
Let's make sure you've compiled the module.

Confirm you compiled the module...do you see a .ko with new timestamp?

Can you sudo modprobe <drivername> ?
Or sudo insmod drivername.ko ?

(at this point you don't need to keep rebooting the kernel.  We will
modprobe add/remove your driver.)

post what you have on the above items and I'll take a look.

> 2. i went ahead to creating the .git/hooks/pre-commit but when i try 
> staging and commiting the file i get the respective errors:
> 
> error: Invalid path '.git/hooks/pre-commit'
> error: unable to add .git/hooks/pre-commit to index
> fatal: adding files failed
> 
> and
> 
> error: pathspec 'First patch' did not match any file(s) known to git.
> 
> please some one help me out???

You are not submitted that pre-commit hooks file.  It lives in your
git tree to poke you went you make a submittal.

> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/64c3385b-6ee7-44ac-bb17-e265d5f9ade8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

       reply	other threads:[~2016-07-26 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <64c3385b-6ee7-44ac-bb17-e265d5f9ade8@googlegroups.com>
2016-07-26 19:46 ` Alison Schofield [this message]
     [not found]   ` <3c9a93d6-25e0-41ee-bb58-2b29a800200c@googlegroups.com>
2016-07-27  3:40     ` [Outreachy kernel] commiting the .git/hooks/pre-commit and testing the changes on the updated e1000_main.c Alison Schofield
2016-07-27  3:49       ` Alison Schofield

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=20160726194613.GA14874@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=courageangeh@gmail.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.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