All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH 0/6] xhci features and fixes for usb-next
Date: Thu, 22 Sep 2022 14:08:18 +0200	[thread overview]
Message-ID: <YyxQMtJCLdgWuCsu@kroah.com> (raw)
In-Reply-To: <20220921123450.671459-1-mathias.nyman@linux.intel.com>

On Wed, Sep 21, 2022 at 03:34:44PM +0300, Mathias Nyman wrote:
> Hi Greg
> 
> Some xhci features and fixes for usb-next.
> Both fixing some possible memory leaks that are too late for usb-linus,
> and simple code cleanups for usb-next

Did you miss this one:
	https://lore.kernel.org/r/20220915011134.58400-1-liulongfang@huawei.com

or was there some issue with it?

thanks,

greg k-h

  parent reply	other threads:[~2022-09-22 12:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 12:34 [PATCH 0/6] xhci features and fixes for usb-next Mathias Nyman
2022-09-21 12:34 ` [PATCH 1/6] usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info() Mathias Nyman
2022-09-21 12:34 ` [PATCH 2/6] xhci: dbc: Fix memory leak in xhci_alloc_dbc() Mathias Nyman
2022-09-21 12:34 ` [PATCH 3/6] xhci: Don't show warning for reinit on known broken suspend Mathias Nyman
2022-09-21 12:34 ` [PATCH 4/6] xhci: show fault reason for a failed enable slot command Mathias Nyman
2022-09-21 12:34 ` [PATCH 5/6] xhci: remove unused command member from struct xhci_hcd struct Mathias Nyman
2022-09-21 12:34 ` [PATCH 6/6] xhci: remove unused lpm_failed_dev member from struct xhci_hcd Mathias Nyman
2022-09-22 12:08 ` Greg KH [this message]
2022-09-22 12:43   ` [PATCH 0/6] xhci features and fixes for usb-next Mathias Nyman
2022-09-22 12:52     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2021-08-20 12:34 Mathias Nyman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YyxQMtJCLdgWuCsu@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.