1. 19 5月, 2010 2 次提交
  2. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  3. 16 12月, 2009 1 次提交
  4. 06 12月, 2009 1 次提交
  5. 17 6月, 2009 2 次提交
  6. 30 3月, 2009 3 次提交
  7. 03 1月, 2009 3 次提交
  8. 30 12月, 2008 1 次提交
  9. 22 10月, 2008 2 次提交
  10. 12 10月, 2008 4 次提交
  11. 27 7月, 2008 1 次提交
  12. 26 7月, 2008 1 次提交
  13. 24 7月, 2008 1 次提交
  14. 20 7月, 2008 1 次提交
  15. 29 4月, 2008 1 次提交
    • H
      media: fix integer as NULL pointer warnings · a6a3a17b
      Harvey Harrison 提交于
      drivers/media/video/v4l2-common.c:719:16: warning: Using plain integer as NULL pointer
      drivers/media/video/au0828/au0828-dvb.c:122:19: warning: Using plain integer as NULL pointer
      drivers/media/video/ivtv/ivtv-yuv.c:1101:22: warning: Using plain integer as NULL pointer
      drivers/media/video/ivtv/ivtv-yuv.c:1102:23: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-audio.c:78:39: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-video-v4l.c:84:39: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-v4l2.c:1264:9: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-context.c:197:28: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-cx2584x-v4l.c:126:39: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-dvb.c:133:32: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-dvb.c:145:31: warning: Using plain integer as NULL pointer
      drivers/media/video/pvrusb2/pvrusb2-dvb.c:177:55: warning: Using plain integer as NULL pointer
      drivers/media/video/videobuf-core.c:100:9: warning: Using plain integer as NULL pointer
      Signed-off-by: NHarvey Harrison <harvey.harrison@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a6a3a17b
  16. 25 4月, 2008 5 次提交
    • M
      V4L/DVB (7723): pvrusb2: Clean up input selection list generation in V4L interface · e57b1c80
      Mike Isely 提交于
      Change how list of possible pvrusb2 inputs is generated to include
      only those interfaces that make sense for the interface instance.
      Signed-off-by: NMike Isely <isely@pobox.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      e57b1c80
    • M
      V4L/DVB (7719): pvrusb2: Implement input selection enforcement · 1cb03b76
      Mike Isely 提交于
      In the pvrusb2 driver, different interfaces (e.g. V4L, DVB) have
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      1cb03b76
    • M
      V4L/DVB (7321): pvrusb2: Rework context handling and initialization · 794b1607
      Mike Isely 提交于
      This change significantly rearranges pvr2_context level initialization
      and operation:
      
      1. A new kernel thread is set up for management of the context.
      
      2. Destruction of the pvr2_context instance is moved into the kernel
         thread.  No other context is able to remove the instance; doing
         this simplifies lock handling.
      
      3. The callback into pvrusb2-main, which is used to trigger
         initialization of each interface, is now issued from this kernel
         thread.  Previously it had been indirectly issued out of the work
         queue thread in pvr2_hdw, which led to deadlock issues if the
         interface needed to change a control setting (which in turn
         requires dispatch of another work queue entry).
      
      4. Callbacks into the interfaces (via the pvr2_channel structure) are
         now issued strictly from this thread.  The net result of this is
         that such callback functions can now also safely operate driver
         controls without deadlocking the work queue.  (At the moment this
         is not actually a problem, but I'm anticipating issues with this in
         the future).
      
      5. There is no longer any need for anyone to enter / exit the
         pvr2_context structure.  Implementation of the kernel thread here
         allows this all to be internal now, simplifying other logic.
      
      6. A very very longstanding issue involving a mutex deadlock between
         the pvrusb2 driver and v4l should now be solved.  The deadlock
         involved the pvr2_context mutex and a globals-protecting mutex in
         v4l.  During initialization the driver would take the pvr2_context
         mutex first then the v4l2 interface would register with v4l and
         implicitly take the v4l mutex.  Later when v4l would call back into
         the driver, the two mutexes could possibly be taken in the opposite
         order, a situation that can lead to deadlock.  In practice this
         really wasn't an issue unless a v4l app tried to start VERY early
         after the driver appeared.  However it still needed to be solved,
         and with the use of the kernel thread relieving need for
         pvr2_context mutex, the problem should be finally solved.
      Signed-off-by: NMike Isely <isely@pobox.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      794b1607
    • M
      V4L/DVB (7300): pvrusb2: v4l2 implementation fixes for input selection · beb0ecd7
      Mike Isely 提交于
      Now that the pvrusb2 driver can dynamically choose which inputs to
      make available depending on the hardware, the enumeration of input
      choices is no longer a contiguous range of integers.  Unfortunately
      this causes a problem in the v4l2 implementation since the input
      enumeration requires continuity in the API.  This change implements a
      mapping in order to preserve the v4l2 interface requirement.
      Signed-off-by: NMike Isely <isely@pobox.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      beb0ecd7
    • M
      V4L/DVB (7298): pvrusb2: Account for dtv choice (a bit) in v4l2 implementation · 895c3e8b
      Mike Isely 提交于
      The v4l2 implementation in pvru2b2 must produce a sane answer when
      asked, when the input choice is set to dtv.
      Signed-off-by: NMike Isely <isely@pobox.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      895c3e8b
  17. 26 1月, 2008 2 次提交
    • M
      V4L/DVB (6695): pvrusb2: Implement functions to pass descriptive hardware info · 78a47101
      Mike Isely 提交于
      Implement additional pvrusb2 device info table entries for a device
      identifier and a device description.  Export this information via the
      driver's internal API.  Make this information available via the sysfs
      driver interface.  Also propagate this information into the v4l2
      capability structure.  An app can now retrieve and report a
      descriptive string about the particular type of hardware device it is
      operating.
      Signed-off-by: NMike Isely <isely@pobox.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      78a47101
    • M
      V4L/DVB (6691): pvrusb2: Rework pipeline state control · 681c7399
      Mike Isely 提交于
      This is a new implementation for video pipeline control within the
      pvrusb2 driver.  Actual start/stop of the pipeline is moved to the
      driver's kernel thread.  Pipeline stages are controlled autonomously
      based on surrounding pipeline or application control state.  Kernel
      thread management is also cleaned up and moved into the internal
      control structure of the driver, solving a set up / tear down race
      along the way.  Better failure recovery is implemented with this new
      control strategy.  Also with this change comes better control of the
      cx23416 encoder, building on additional information learned about the
      peculiarities of controlling this part (this information was the
      original trigger for this rework).  With this change, overall encoder
      stability should be considerably improved.  Yes, this is a large
      change for this driver, but due to the nature of the feature being
      worked on, the changes are fairly pervasive and would be difficult to
      break into smaller pieces with any semblence of step-wise stability.
      Signed-off-by: NMike Isely <isely@pobox.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      681c7399
  18. 22 10月, 2007 1 次提交
  19. 28 4月, 2007 1 次提交
  20. 15 3月, 2007 1 次提交
  21. 01 3月, 2007 1 次提交
  22. 21 2月, 2007 4 次提交