All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Josue David Hernandez Gutierrez  <josue.d.hernandez.gutierrez@intel.com>
Cc: linux-usb@vger.kernel.org, mathias.nyman@linux.intel.com
Subject: Re: [PATCH 1/2] usb: host: xhci: Remove msi irq reconfigure on resume
Date: Tue, 29 Mar 2022 18:11:09 +0200	[thread overview]
Message-ID: <YkMvnWBDDFCkLAJs@kroah.com> (raw)
In-Reply-To: <20220329154406.5485-1-josue.d.hernandez.gutierrez@intel.com>

On Tue, Mar 29, 2022 at 09:44:05AM -0600, Josue David Hernandez Gutierrez wrote:
> xhci_resume function is cleaning up msi irqs to avoid
> conflicts when xhci_run is called, because xhci_run
> is going to setup those msi irqs and it is called at
> the end of xhci_resume, then creating a new start
> callback for the xhci-pci driver to setup msi
> irqs and removing this msi irq setup from xhci_run
> reconfigure msi irqs won't be needed in xhci_resume.

You do have a full 72 columns to use in your changelog body :)

> This change also allows us move the msi setup code to
> the correct place, that is from xhci.c to xhci-pci.c

When you have "also" in a changelog text, it almost always means it
should be multiple patches.

Please break this up into "move the code" and "modify the code" patches
to make it easier to review.

As it is, it's pretty impossible to notice if anything has changed in
the logic or not.

Would you want to review this?

thanks,

greg k-h

      parent reply	other threads:[~2022-03-29 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 15:44 [PATCH 1/2] usb: host: xhci: Remove msi irq reconfigure on resume Josue David Hernandez Gutierrez
2022-03-29 15:44 ` [PATCH 2/2] usb: host: xhci: Move msi/msi-x functions to xhci-pci Josue David Hernandez Gutierrez
2022-03-29 16:12   ` Greg KH
2022-03-30  7:36     ` Mathias Nyman
2022-03-29 16:11 ` Greg KH [this message]

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=YkMvnWBDDFCkLAJs@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=josue.d.hernandez.gutierrez@intel.com \
    --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.