01 Nov, 2011

1 commit


20 Apr, 2008

1 commit


08 Apr, 2008

1 commit

  • Every current transport class calls transport_container_release but
    ignores the return value. This is catastrophic if it returns an error
    because the containers are part of a global list and the next action of
    almost every transport class is to free the memory used by the
    container.

    Fix this by making transport_container_release a void, but making it BUG
    if attribute_container_release returns an error ... this catches the
    root cause of a system panic much earlier. If we don't do this, we get
    an eventual BUG when the attribute container list notices the corruption
    caused by the freed memory it's still referencing.

    Also made attribute_container_release __must_check as a reminder.

    Cc: Greg KH
    Signed-off-by: James Bottomley

    James Bottomley
     

04 Mar, 2008

1 commit


29 Aug, 2005

1 commit

  • If your transport class sets the ATTRIBUTE_CONTAINER_NO_CLASSDEVS flag,
    then its configure method never gets called. This patch fixes that so
    that the configure method is called with a NULL classdev.

    Also remove a spurious inverted comma in the transport_class comments.

    Signed-off-by: James Bottomley

    James Bottomley
     

15 Aug, 2005

1 commit

  • I recently tried to construct a totally generic transport class and
    found there were certain features missing from the current abstract
    transport class. Most notable is that you have to hang the data on the
    class_device but most of the API is framed in terms of the generic
    device, not the class_device.

    These changes are two fold

    - Provide the class_device to all of the setup and configure APIs
    - Provide and extra API to take the device and the attribute class and
    return the corresponding class_device

    Signed-off-by: James Bottomley

    James Bottomley
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds