linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Rohit Sarkar <rohitsarkar5398@gmail.com>
Cc: Hubert CHAUMETTE <hubert.chaumette@kolabnow.com>,
	Oliver Neukum <oneukum@suse.com>,
	linux-usb@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: Re: Beginner query regarding usbhid
Date: Thu, 26 Mar 2020 09:04:09 -0700	[thread overview]
Message-ID: <f6b96246-5821-9e54-e816-96f2e1a16cc4@infradead.org> (raw)
In-Reply-To: <5e7c969c.1c69fb81.37131.654a@mx.google.com>

On 3/26/20 4:48 AM, Rohit Sarkar wrote:
> Hi,
> On Wed, Mar 25, 2020 at 11:07:55PM -0700, Randy Dunlap wrote:
>>
>> So /home/rohit/kernels/staging is the top-level kernel source directory?
>>
>> "M=dir" is for external modules to be built.  AFAICT you are not building any
>> external modules.
>>
>> Just run
>> $ cd <top of kernel source tree>
>> $ make all
>> $ sudo make install
> 
> Wow it worked now.
> I ran make and make modules_install install. After that I restarted the
> system.
> 
> Does this mean everytime I do some changes to an intree module I need to
> reboot my system?

No, that should not be necessary.

-- 
~Randy


      reply	other threads:[~2020-03-26 16:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 13:42 Beginner query regarding usbhid Rohit Sarkar
2020-03-25 14:45 ` Oliver Neukum
2020-03-25 14:47   ` Rohit Sarkar
2020-03-25 15:41     ` Hubert CHAUMETTE
2020-03-25 17:13       ` Rohit Sarkar
2020-03-25 21:40         ` Randy Dunlap
2020-03-26  5:31           ` Rohit Sarkar
2020-03-26  6:07             ` Randy Dunlap
2020-03-26  6:53               ` Rohit Sarkar
2020-03-26 15:56                 ` Randy Dunlap
2020-03-26  7:34               ` Rohit Sarkar
2020-03-26 16:02                 ` Randy Dunlap
2020-03-26 16:14                   ` Rohit Sarkar
2020-03-26 16:16                     ` Randy Dunlap
2020-03-26 11:48               ` Rohit Sarkar
2020-03-26 16:04                 ` Randy Dunlap [this message]

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=f6b96246-5821-9e54-e816-96f2e1a16cc4@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=hubert.chaumette@kolabnow.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=rohitsarkar5398@gmail.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;
as well as URLs for NNTP newsgroup(s).