From: Bharath Vedartham <linux.bhar@gmail.com>
To: valdis.kletnieks@vt.edu
Cc: Himanshu Jha <himanshujha199640@gmail.com>,
kernelnewbies@kernelnewbies.org
Subject: Re: drivers: iio: Adding channels to the simple_dummy module
Date: Sat, 26 Jan 2019 12:12:07 +0530 [thread overview]
Message-ID: <20190126064207.GA3279@bharath12345-Inspiron-5559> (raw)
In-Reply-To: <991.1548433473@turing-police.cc.vt.edu>
On Fri, Jan 25, 2019 at 11:24:33AM -0500, valdis.kletnieks@vt.edu wrote:
> On Fri, 25 Jan 2019 17:11:25 +0530, Bharath Vedartham said:
> > On Thu, Jan 24, 2019 at 04:21:32PM +0530, Himanshu Jha wrote:
> > > Well, you can try other email clients such as Evolution, Claws ...
> > >
> > > There is no rule saying to use Mutt exclusively.
>
> > VM has low RAM. Need to adjust :)
>
> Upgrade the hypervisor system so the VM can be properly configured :)
>
I think I ll rather build a native version. The reason I chose a VM was
cause I was told that if I break the kernel it would be much safer. But
I think GRUB will save my life if I screw things up. Thanks for your
time!
> (As a side note, few people send their diffs from inside their test VM.
> They usually build outside the VM and copy the needed pieces into
> a shared area that the build environment and the VM can both see.)
That is an interesting usecase. I wonder why they need to do that?
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-01-26 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 18:03 drivers: iio: Adding channels to the simple_dummy module Bharath Vedartham
2019-01-23 11:06 ` Himanshu Jha
2019-01-23 17:58 ` Bharath Vedartham
2019-01-24 10:51 ` Himanshu Jha
2019-01-25 11:41 ` Bharath Vedartham
2019-01-25 16:24 ` valdis.kletnieks
2019-01-26 6:42 ` Bharath Vedartham [this message]
2019-01-26 18:39 ` valdis.kletnieks
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=20190126064207.GA3279@bharath12345-Inspiron-5559 \
--to=linux.bhar@gmail.com \
--cc=himanshujha199640@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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).