1. 17 2月, 2010 16 次提交
  2. 14 1月, 2010 1 次提交
  3. 07 10月, 2009 1 次提交
  4. 01 4月, 2009 1 次提交
  5. 27 2月, 2009 1 次提交
  6. 17 10月, 2008 1 次提交
  7. 14 10月, 2008 1 次提交
  8. 23 7月, 2008 1 次提交
  9. 22 7月, 2008 1 次提交
  10. 21 7月, 2008 1 次提交
    • A
      tty: Ldisc revamp · a352def2
      Alan Cox 提交于
      Move the line disciplines towards a conventional ->ops arrangement.  For
      the moment the actual 'tty_ldisc' struct in the tty is kept as part of
      the tty struct but this can then be changed if it turns out that when it
      all settles down we want to refcount ldiscs separately to the tty.
      
      Pull the ldisc code out of /proc and put it with our ldisc code.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a352def2
  11. 21 6月, 2008 1 次提交
  12. 30 4月, 2008 1 次提交
  13. 28 4月, 2008 1 次提交
    • H
      capi: fix sparse warnings using integer as NULL pointer · 2f9e9b6d
      Harvey Harrison 提交于
      drivers/isdn/capi/kcapi.c:829:30: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/kcapi.c:838:27: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/kcapi.c:954:17: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/kcapi.c:1007:37: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/kcapi.c:1009:33: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capiutil.c:453:24: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capilib.c:47:30: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:353:29: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:369:15: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:486:48: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:515:46: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:541:47: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:692:47: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:699:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:704:14: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:943:53: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:948:32: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:969:42: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:989:48: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:1026:69: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:1028:19: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:1061:20: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:1529:37: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capi.c:1531:33: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:338:15: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:758:32: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:880:40: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:407:15: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:429:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:407:15: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:444:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:429:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:429:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:429:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:429:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:429:49: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:1664:61: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:1969:37: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:2294:37: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:2297:33: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:2338:37: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capidrv.c:2341:33: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capifs.c:192:37: warning: Using plain integer as NULL pointer
      drivers/isdn/capi/capifs.c:194:33: warning: Using plain integer as NULL pointer
      Signed-off-by: NHarvey Harrison <harvey.harrison@gmail.com>
      Cc: Karsten Keil <kkeil@suse.de>
      Cc: Jeff Garzik <jeff@garzik.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      2f9e9b6d
  14. 25 1月, 2008 1 次提交
  15. 18 7月, 2007 1 次提交
    • A
      isdn/capi warning fixes · 5e6c20a9
      Andrew Morton 提交于
      drivers/isdn/capi/capi.c: In function 'handle_minor_send':
      drivers/isdn/capi/capi.c:552: warning: cast from pointer to integer of different size
      
      Of course, the code here might actually be buggy, in which case this patch
      should not be applied?
      
      Answer:
      
        No this field is ignored inside linux kernel.Yes this is ugly, but it's
        the CAPI spec for all OS.
      
        CAPI DATA_B3 Request/Indication CAPI Message has a mandatory field which
        represent the 32 bit buffer address of the payload data.  In linux the
        payload data do not use a sperate buffer, data follows directely after the
        CAPI Message in the same skb and we use this assumption inside the drivers,
        so we can ignore this field.
      
        Inside the linux CAPI implemetation we never use this field, so it could
        also have no value, but since random data in a message is bad as well (e.g.
        displayed in CAPI traces) we set is to the most adequate value.
      
        Outside the kernel the capi20 library sets the correct addresses (there is
        an optional second field for 64 bit adresses for 64 bit systems, we do not
        use here).
      Acked-by: NKarsten Keil <kkeil@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      5e6c20a9
  16. 09 5月, 2007 2 次提交
  17. 13 2月, 2007 3 次提交
  18. 09 12月, 2006 3 次提交
  19. 02 10月, 2006 1 次提交
    • J
      [PATCH] const struct tty_operations · b68e31d0
      Jeff Dike 提交于
      As part of an SMP cleanliness pass over UML, I consted a bunch of
      structures in order to not have to document their locking.  One of these
      structures was a struct tty_operations.  In order to const it in UML
      without introducing compiler complaints, the declaration of
      tty_set_operations needs to be changed, and then all of its callers need to
      be fixed.
      
      This patch declares all struct tty_operations in the tree as const.  In all
      cases, they are static and used only as input to tty_set_operations.  As an
      extra check, I ran an i386 allyesconfig build which produced no extra
      warnings.
      
      53 drivers are affected.  I checked the history of a bunch of them, and in
      most cases, there have been only a handful of maintenance changes in the
      last six months.  serial_core.c was the busiest one that I looked at.
      Signed-off-by: NJeff Dike <jdike@addtoit.com>
      Acked-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b68e31d0
  20. 01 7月, 2006 1 次提交