Prev: Staging: dt3155: fix coding style issues in dt3155_drv.c
Next: linux-next: manual merge of the v4l-dvb tree with Linus' tree
From: David Miller on 5 Jul 2010 22:00
From: Tilman Schmidt <tilman(a)imap.cc>
Date: Tue, 6 Jul 2010 02:18:32 +0200 (CEST)

> Karsten, David,
>
> following are a series of patches to the Gigaset driver I'd like
> to see included in kernel release 2.6.36.

Do they have any dependencies on the two patch set of fixes
you just sent out for net-2.6?

You must always let me know this so I don't go blindly trying
to apply your patches onto to find that they don't apply cleanly
because of a dependency you have failed to mention.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Tilman Schmidt on 6 Jul 2010 03:50
Am 2010-07-06 03:53 schrieb David Miller:
> From: Tilman Schmidt <tilman(a)imap.cc>
> Date: Tue, 6 Jul 2010 02:18:32 +0200 (CEST)
>
>> Karsten, David,
>>
>> following are a series of patches to the Gigaset driver I'd like
>> to see included in kernel release 2.6.36.
>
> Do they have any dependencies on the two patch set of fixes
> you just sent out for net-2.6?

None. They are completely independent.

I guess your question arose because I gave both series the same
title by mistake. The second one should have been called:
"*Gigaset* patches for 2.6.36".

Thanks,
Tilman

 | 
Pages: 1
Prev: Staging: dt3155: fix coding style issues in dt3155_drv.c
Next: linux-next: manual merge of the v4l-dvb tree with Linus' tree