[PATCH 0/5] staging: vc04_services: camera driver maintance

Michael Zoran mzoran at crowfest.net
Mon Mar 20 07:53:18 PDT 2017

On Mon, 2017-03-20 at 16:57 +0300, Dan Carpenter wrote:
> On Mon, Mar 20, 2017 at 04:06:00AM -0700, Michael Zoran wrote:
> > On Mon, 2017-03-20 at 13:55 +0300, Dan Carpenter wrote:
> > > I'm not going to review this because it has kbuild errors.
> > > 
> > > regards,
> > > dan carpenter
> > > 
> > 
> > Hi, can you e-mail out the errors or send them to me.  It worked
> > when
> > I submitted it.
> > 
> The problem is that you added a function only for ARM but the camera
> can build on i386.
> Anyway, we need to figure out why you aren't getting the kbuild
> emails
> and fix that.  I forwarded the first email to you.  The other is
> basically the same.
> regards,
> dan carpenter

OK, thanks for sending it to me.

I don't quite understand how that is possible in all since the whole
subtree depends on RASPBERRYPI_FIRMWARE which I had nothing to do with
setting up.  Sounds to me like the real issue here is that the
RASPBERRYPI_FIRMARE driver wasn't setup correctly in the first place. 
I also noticed when I was trying to understand how the raspberrypi
driver works in the first place in that it doesn't always dump the
firmware revision correctly if the DT node mbox handle gets pointed to
who knows where.

I've been complaining about very selective e-mails on so called public
e-mail lists for a very long time now, and nobody has done anything
about it. Sometimes I don't get any e-mail for a week and then I'll get
a flood of e-mail thats 2 weeks old.  And who knows which e-mails lists
changes are going to. Some changes are getting in under the radar by
others and other changes have every line criticized.

I have been honestly testing all the changes I have submitted, and most
of them have been small.  But they have caused things to work when they
don't work at all before.  

More information about the linux-rpi-kernel mailing list