1. 10 11月, 2009 7 次提交
  2. 09 11月, 2009 4 次提交
  3. 08 11月, 2009 4 次提交
  4. 07 11月, 2009 5 次提交
    • T
      ALSA: hda - Don't initialize CORB/RIRB for single_cmd mode · 1a696978
      Takashi Iwai 提交于
      So far, CORB/RIRB still remains even if the driver is switched to the
      single_cmd mode.  The specification says that this should be disabled,
      but I hoped this isn't the case; indeed most devices worked together with
      CORB/RIRB.
      
      However, Poulsbo (US15W) seems problematic with this setup, and it
      requires to disable CORB/RIRB when single_cmd is used.
      
      Now this patch disables CORB/RIRB initialization when the single_cmd
      mode is used.  Also the unsolicited event is disabled because it can't
      work without RIRB.
      Reported-and-tested-by: NTroy Kisky <troy.kisky@boundarydevices.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      1a696978
    • J
      ALSA: usb-audio: fix combine_word problem · f4950882
      Julian Anastasov 提交于
      Fix combine_word problem where first octet is not
      read properly. The only affected place seems to be the
      INPUT_TERMINAL type. Before now, sound controls can be created
      with the output terminal's name which is a fallback mechanism
      used only for unknown input terminal types. For example,
      Line can wrongly appear as Speaker. After the change it
      should appear as Line.
      
      	The side effect of this change can be that users
      can expect the wrong control name in their scripts or
      programs while now we return the correct one.
      
      	Probably, these defines should use get_unaligned_le16 and
      friends.
      Signed-off-by: NJulian Anastasov <ja@ssi.bg>
      Cc: <stable@kernel.org>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      f4950882
    • T
      sound: Replace old style lock initializer · 70edc800
      Thomas Gleixner 提交于
      SPIN_LOCK_UNLOCKED is deprecated. Use __SPIN_LOCK_UNLOCKED instead.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      70edc800
    • J
      cifs: don't use CIFSGetSrvInodeNumber in is_path_accessible · f475f677
      Jeff Layton 提交于
      Because it's lighter weight, CIFS tries to use CIFSGetSrvInodeNumber to
      verify the accessibility of the root inode and then falls back to doing a
      full QPathInfo if that fails with -EOPNOTSUPP. I have at least a report
      of a server that returns NT_STATUS_INTERNAL_ERROR rather than something
      that translates to EOPNOTSUPP.
      
      Rather than trying to be clever with that call, just have
      is_path_accessible do a normal QPathInfo. That call is widely
      supported and it shouldn't increase the overhead significantly.
      
      Cc: Stable <stable@kernel.org>
      Signed-off-by: NJeff Layton <jlayton@redhat.com>
      Signed-off-by: NSteve French <sfrench@us.ibm.com>
      f475f677
    • J
      cifs: clean up handling when server doesn't consistently support inode numbers · ec06aedd
      Jeff Layton 提交于
      It's possible that a server will return a valid FileID when we query the
      FILE_INTERNAL_INFO for the root inode, but then zeroed out inode numbers
      when we do a FindFile with an infolevel of
      SMB_FIND_FILE_ID_FULL_DIR_INFO.
      
      In this situation turn off querying for server inode numbers, generate a
      warning for the user and just generate an inode number using iunique.
      Once we generate any inode number with iunique we can no longer use any
      server inode numbers or we risk collisions, so ensure that we don't do
      that in cifs_get_inode_info either.
      
      Cc: Stable <stable@kernel.org>
      Reported-by: NTimothy Normand Miller <theosib@gmail.com>
      Signed-off-by: NJeff Layton <jlayton@redhat.com>
      Signed-off-by: NSteve French <sfrench@us.ibm.com>
      ec06aedd
  5. 06 11月, 2009 20 次提交