On Llu, 2005-11-14 at 15:34 +0800, Luke Yang wrote: > So the process is: when kernel release a new version, we should > update our arch related files to the new kernel, then send you the > patch. Am I right? That is the ideal case. Also in theory nothing major should change after -rc1 of each release so nothing should break later on. Not all of the minor trees work every release but its considered better if they do. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- ADI Blackfin patch for kernel 2.6.14
- From: Luke Yang <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Adrian Bunk <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Luke Yang <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Luke Yang <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Greg KH <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Luke Yang <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Greg KH <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Andrew Morton <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Luke Yang <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Greg KH <[email protected]>
- Re: ADI Blackfin patch for kernel 2.6.14
- From: Luke Yang <[email protected]>
- ADI Blackfin patch for kernel 2.6.14
- Prev by Date: Re: Nick's core remove PageReserved broke vmware...
- Next by Date: Re: [2.6 patch] i386: always use 4k stacks
- Previous by thread: Re: ADI Blackfin patch for kernel 2.6.14
- Next by thread: Re: ADI Blackfin patch for kernel 2.6.14
- Index(es):
 |