Re: linux-next: net/kbuild trees build failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Dec 07, 2009 at 05:28:53PM -0500, John W. Linville wrote:
> On Mon, Dec 07, 2009 at 10:42:09PM +0100, Michal Marek wrote:
> > reinette chatre napsal(a):
> 
> > > Right - could we please use the solution that works at compile time? I
> > > used UTS_RELEASE after learning about its use in init/version.c, would
> > > that not make it an approved solution?
> > 
> > It seems there is some misunderstanding.
> 
> Alright, if Stephen's fix is acceptable then your suggestion is fine.
> Sam seemed to suggest that Stephen's fix was a stop-gap.

The need to use utsrelease seems very prominent in external drivers.
But a quick grep turned up only a single staging driver in-tree that
include utsrelease.
So whatever problem this driver solves using utsrelease it is not shared
with the rest of the in-tree drivers.

So no - it is not a stop-gap. It is more a "is it really needed?".

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux