[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120620.025837.721158723130014230.davem@davemloft.net>
Date: Wed, 20 Jun 2012 02:58:37 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: federico.vaga@...il.com
Cc: mkl@...gutronix.de, bhupesh.sharma@...com, sfr@...b.auug.org.au,
netdev@...r.kernel.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, giancarlo.asnaghi@...com,
wg@...ndegger.com
Subject: Re: linux-next: build failure after merge of the net-next tree
From: Federico Vaga <federico.vaga@...il.com>
Date: Wed, 20 Jun 2012 11:59:26 +0200
>> Then the driver should NEVER have been submitted without the
>> required infrastructure in place first.
>
> This particular driver don't use the clk framework at the moment. I put
> that lines about clk to try to be generic as possibile, but I see that I
> made a mistake: I'm sorry.
Why would you try to be generic by using an interface currently
only available on certain platforms?
That is how you make drivers non-portable, and not generic.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists