As you say, I think it could be good to put it into staging so we have a driver in place and then we can continue discussing the architecture from there. /P-G > -----Original Message----- > From: Linus Walleij [mailto:linus.walleij@xxxxxxxxxx] > Sent: den 28 februari 2011 23:44 > To: Vitaly Wool; Par-Gunnar Hjalmdahl > Cc: Par-Gunnar HJALMDAHL; Samuel Ortiz; Marcel Holtmann; Lee Jones; > Alan Cox; Arnd Bergmann; linux-bluetooth@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx; Lukasz Rymanowski; Pavan Savoy > Subject: Re: [PATCH 00/11] mfd and bluetooth: Add CG2900 suppor > > On Fri, Feb 25, 2011 at 6:55 PM, Vitaly Wool <vitalywool@xxxxxxxxx> > wrote: > > > Making hardware work is, if course, a valid point, but porting a > windows > > driver would do that as well, and it's not the reason to pull windows > > drivers' ports into mainline. > > Yeah hm, that sounds like it has "drivers/staging" printed all over it > then, > so either we solve these issues or we need to put it into staging so we > can get help from others in fixing it up (we have a similar situation > with > the U8500 graphics stuff). > > P-G do you think it would be proper to take this into staging for the > moment, or do you prefer to drive it outside the mainline kernel tree > until > it lands in the proper place(s)? > > Yours, > Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html