Ben Hutchings <b...@decadent.org.uk> writes: > On Wed, 2010-06-02 at 10:39 +0200, Bjørn Mork wrote: > >> I am still unsure about the preferred way to provide such a driver >> patch. The first version attached to the bug was just a copy of the >> upstream version with the necessary modifications to make it build under >> 2.6.32. >> >> I have now done the job identifying which commits created the current >> upstream version, and instead provided a patch set consisting of cherry >> picked upstream commits. Is this preferred, even though it results in a >> high number of patches (120 to be exact)? It keeps a lot of meta data, >> which I guess is useful. > [...] > > We can use either form. In this case, where there were several drivers > involved, your patch set was very helpful.
Thanks for looking at it, and for providing this feedback. Nice to know for the next time I go out and buy some new hardware without checking which kernel release the driver was added :-) Bjørn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zkzcd39y....@nemi.mork.no
