On Wed, Nov 21, 2012 at 02:47:15AM -0500, devendra.aaru wrote:
that maintainer's tree is next tree so that next can pickup. once the
next pics up your changes gets merged there in next.
always its good to work against' maintainers trees, if its a fix then
its better work on the maintainer's
Kumar amit mehta gmate.a...@gmail.com wrote:
On Wed, Nov 21, 2012 at 02:47:15AM -0500, devendra.aaru wrote:
that maintainer's tree is next tree so that next can pickup. once
the
next pics up your changes gets merged there in next.
always its good to work against' maintainers trees, if its
Hi, Josh,
Thanks again!
While your suggestion works, it has some disadvantages; maybe
you/someone can advice:
1) In the case when I want to apply a series of patches, let's say a
patchset of 10 patches, does this mean that I should run
pipe git am on each of them ?
2) Even this is the case;
I have searched using google for information regarding linux driver
development and have found a lot, but not the answers to these questions:
* Can 2 different kernel drivers access the same device at the same time?
* Is every driver known as a kernel module?
Basically I need advice on if I can
On Tue, Nov 20, 2012 at 07:24:28PM +0200, Kevin Wilson wrote:
Hi,
I am following some kernel mailing lists (netdev and others).
I want to be able to save recent patches and to apply the against a git tree.
I tried using MUTT client for this. I save the patch (which is almost
always inline).
On Wed, Nov 21, 2012 at 1:11 PM, Christopher Biessener
christophe...@voomtech.com wrote:
I have searched using google for information regarding linux driver
development and have found a lot, but not the answers to these questions:
* Can 2 different kernel drivers access the same device at the
thanks!
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Thu, Nov 22, 2012 at 10:12 AM, horse_rivers horse_riv...@126.com wrote:
thanks!
kmalloc allocates memory from slab cache. It tends to be physically
contigous and you can get memory size smaller than page size.
vmalloc, on the other hand, is when you need only virtually contigous
memory area.
don't top post, ok? :)
ok:）
And good luck. Don't forget to share your progress, ok? ;)
of cource!
as you say,the current gcc do not support some code,
for example : 1. inline asm code form
2. CFLAG can not pass to subdirs
my process is continuing . :)
kmalloc allocates physically contiguous memory, while vmalloc
allocates memory which is only virtually contiguous and not
necessarily physically contiguous.
Usually physically contiguous memory is required for hardware devices
(dma etc) , thus kmalloc is useful for allocating such memory. And
10 matches
Mail list logo
