Hi Greg,
On Wed, 26 Jan 2011 03:23:42 +0100, Greg KH <gregkh@xxxxxxx> wrote:
On Tue, Jan 25, 2011 at 04:13:56PM +0100, Arend van Spriel wrote:
Hi Greg,
On Tue, 25 Jan 2011 15:58:54 +0100, Greg KH <gregkh@xxxxxxx> wrote:
>On Tue, Jan 25, 2011 at 02:32:05PM +0100, Arend van Spriel wrote:
>>Remove differences in util sources for the two supported drivers
>
>But this patch also makes it possible for both to be build at the same
>time, right? Which should be called out here.
>
PATCH 2 makes it possible to build the drivers at the same time, but
I have to change that as it uses symbolic links iso include.
>Why not make that its own patch?
>
>>and remove default print statements.
>
>Ah, you used "and". This means you should not be doing this all in one
>patch.
>
Ok. This means you want me to split and resubmit this patch?
Yes please. Actually resend the whole series, as I had comments on most
of them, right?
For the first patch your reply contained the question whether it should
be in the final .38 release. We are getting confused over here about the
distribution of patches in branches/repositories within the community so
could you elaborate a little and answer my questions below.
1. From the various response I see following submit possibilities:
- staging-next -> patch to you (ie. gregkh@xxxxxxx)
- staging-linus -> patch to you (ie. gregkh@xxxxxxx)
- linus tree -> ??
- stable -> patch to stable@xxxxxxxxxx
- final .38 -> ??
2. For the last three targets it is unclear what repo/branch we need to use
to create our patch upon.
3. For the stable tree it suggest to add Cc: stable@xxxxxxxxxx and add
the upstream (linus tree) commit id. Is this something you will add
when we request it to be applied to those trees or does it require
a separate patch email sent by us?
thanks,
greg k-h
Hope you can eradicate our confusion.
Gr. AvS
--
"The most merciful thing in the world, I think, is the inability of the
human
mind to correlate all its contents." - "The Call of Cthulhu"
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
