On Fri, 19 Sep 2014 09:28:03 +0800, Kinka Huang said:
> @valdis, I am doing that on a laptop. I try to get back the file by
> deleting unpack.h and checkout, but the same content remains. And `git
That's weird indeed.
> status` or `git log` doesn't show any changes of file "unpack.h" . One
> susp
@sudip, I used the same config file before this tag and no problem.
The whole config file maybe too much, can you tell me which part to
post? I will post the file later.
@valdis, I am doing that on a laptop. I try to get back the file by
deleting unpack.h and checkout, but the same content remains
pranay sharma gmail.com> writes:
> I am trying to ramp up on linux kernel and dive deep into network code.
Any pointers on this will be really helpful.
As a real newbie myself, what I've read on multiple sources is:
Do the eudyptula challenge. And that's what I'm doing right now, plus a
bunc
Hi Folks,
You might be getting this a lot.
I am trying to ramp up on linux kernel and dive deep into network code.
Any pointers on this will be really helpful.
I am pretty new to this group and hence might have missed, earlier
mails if any, on similar topic
Thanks in advance!!
Regards,
Pranay.
On Thu, 18 Sep 2014 22:19:40 +0800, Kinka Huang said:
> In file included from drivers/gpu/drm/nouveau/core/core/client.c:29:0:
> drivers/gpu/drm/nouveau/core/include/nvif/unpack.h:1:1: error: expected
> identifier or ( before . token
> ../../../nvif/unpack.h
Your tree is somehow corrupted.
On Sep 18, 2014 7:51 PM, "Kinka Huang" wrote:
>
> Hey,
> I just pull linux-master and checkout tag v3.17-rc5. I think
> linux-master should always compiles successfully, but it seems I am wrong?
> I got the error:
can you please post your config file .
thanks
sudip
>
> In file included from driv
On Thu, 18 Sep 2014 06:39:01 -0400, nick said:
> I am trying to run xfs tests on a partion at /dev/sdc1 but the scripts state
> that the drive is not at $TEST_DIR and if '
> it's on that directory they abort after fsck. Does anybody known how to fix
> this please.
It can probably be fixed by rea
Hey,
I just pull linux-master and checkout tag v3.17-rc5. I think
linux-master should always compiles successfully, but it seems I am wrong?
I got the error:
In file included from drivers/gpu/drm/nouveau/core/core/client.c:29:0:
drivers/gpu/drm/nouveau/core/include/nvif/unpack.h:1:1: error: expec
On Thu, 2014-09-18 at 07:57 -0400, Robert P. J. Day wrote:
> On Thu, 18 Sep 2014, Paul Bolle wrote:
> > I try to holler when a new one of these enters linux-next. Very few
> > people seems to share this pet peeve.
>
> i'm pretty sure i had this conversation once upon a time, possibly
> on LKML,
*is*
> > actually defined as a flag in the associated Makefile, which is a
> > *no-no* -- the very established tradition is that the variable prefix
> > "CONFIG_" is reserved for Kconfig variables *only*. if that variable
> > *used* to be set in a Kconfig file, but
the very established tradition is that the variable prefix
> "CONFIG_" is reserved for Kconfig variables *only*. if that variable
> *used* to be set in a Kconfig file, but was subsequently moved to a
> Makefile, tradition suggests the "CONFIG_" prefix should have been
> droppe
On September 18, 2014 6:39:01 AM EDT, nick wrote:
>I am trying to run xfs tests on a partion at /dev/sdc1 but the scripts
>state that the drive is not at $TEST_DIR and if '
>it's on that directory they abort after fsck. Does anybody known how to
>fix this please.
>Thanks,
>Nick
I wrote a simpl
... i've been tidying them up a bit and rerunning them to get
up-to-date output as examples:
http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup_scripts
and as i know greg kh follows this list, i thought the following
output from running the "badref" script on drivers/staging was
interesting
I am trying to run xfs tests on a partion at /dev/sdc1 but the scripts state
that the drive is not at $TEST_DIR and if '
it's on that directory they abort after fsck. Does anybody known how to fix
this please.
Thanks,
Nick
___
Kernelnewbies mailing li
Hello,
I am trying to explore tty drivers. To start with, I am trying to
implement a simple loop back device(testing with echo and cat).
The code works fine as far as write is concerned. When the user process
(echo) calls write() on the device, the driver's write_room() is called
and then writ
15 matches
Mail list logo