Re: Changing the return value of xxx_attach() from void to int.

2016-07-09 Thread John Nemeth
On Jul 10, 2:39am, David Holland wrote: } On Sat, Jul 09, 2016 at 04:57:20PM -0700, John Nemeth wrote: } > A number of people have expressed reservation (bring up memories } > of device_t and how long that took to settle out) indicating that } > this should be done on a branch or something

Re: Changing the return value of xxx_attach() from void to int.

2016-07-09 Thread David Holland
On Sat, Jul 09, 2016 at 04:57:20PM -0700, John Nemeth wrote: > A number of people have expressed reservation (bring up memories > of device_t and how long that took to settle out) indicating that > this should be done on a branch or something. Personally, I don't > see the need to do so.

Re: Changing the return value of xxx_attach() from void to int.

2016-07-09 Thread John Nemeth
On Jun 23, 7:40pm, Masanobu SAITOH wrote: } } As you know, the return value of device driver's attach function is void. } I've thought that we should change it to int for many years. I believe I'm } not the only person. I've been meaning to get back to this one for some time... } xxx_a

Re: GSoC-2016

2016-07-09 Thread HRISHIKESH GOYAL
Hello sir I have partially included the code for the htree indexing write support with no build errors. But I am in a doubt that when will my code will run if file-system is only allowed to mount in ReadOnly mode. Furthermore how will I test and debug htree directory write support if I cant write i

Re: GSoC-2016

2016-07-09 Thread Christos Zoulas
On Jul 9, 10:15pm, hrishi.go...@gmail.com (HRISHIKESH GOYAL) wrote: -- Subject: Re: GSoC-2016 | Hello sir | I have partially included the code for the htree indexing write support | with no build errors. But I am in a doubt that when will my code will run | if file-system is only allowed to mount