All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Rorvick <chris@rorvick.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oneukum@suse.de>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC RESEND 00/10] Create separate header for ehci-dbgp driver
Date: Mon, 3 Nov 2014 15:09:13 -0800	[thread overview]
Message-ID: <20141103230913.GA11259@kroah.com> (raw)
In-Reply-To: <1414984077-9750-1-git-send-email-chris@rorvick.com>

On Sun, Nov 02, 2014 at 09:07:47PM -0600, Chris Rorvick wrote:
> One more attempt at getting some feedback.
> 
> Original:
> 
> The FUSBH200 and FOTG210 are not EHCI-compatible and require standalone
> drivers.  See discussion at:
> 
>   http://comments.gmane.org/gmane.linux.usb.general/84169
> 
> But these controllers do implement an EHCI-compatible debug port and
> therefore leverage the ehci-dbgp driver.  Rather than pulling in the
> necessary declarations from <linux/usb/ehci_def.h>, each driver copies
> this code into their own header.  The goal of this series is to pull the
> ehci-dbgp related code into its own header to remove the need for this
> redundancy.
> 
> I have done only minimal testing on this, and I don't use either of
> these controller so my ability to test the changes is limited.  But I
> thought I'd push it out for comment to see if there was interest.
> 
> The only actual change should be when CONFIG_EARLY_PRINTK_DBGP is
> disabled and CONFIG_XEN_DOM0 is enabled.  Currently each of these does
> not notify Xen of reset events under this configuration.  Since these
> events are propagated when CONFIG_EARLY_PRINTK_DBGP and CONFIG_XEN_DOM0
> are both enabled, though, it seems that is not a problem (and maybe not
> sending them in the former case is a bug?)  Regardless, the motivation
> for this change is for consistancy as a step towrads consolidation.  As
> I said above, I am not able to actually test these changes on either
> controller.
> 
> First time submission, so I look forward to any feedback.  If this is of
> any interest I will work on testing the various configations and boot
> parameters.
> 
> Regards,
> 
> Chris Rorvick
> 
> Chris Rorvick (10):
>   usb: Create separate header for ehci-dbgp
>   fusbh200: Make Xen notificaiton consistent with EHCI
>   fusbh200: Remove superfluous macro definitions
>   fusbh200: Remove duplicate ehci-dbgp declarations
>   fusbh200: Use ehci_dbg_port struct
>   fotg210: Make Xen notificaiton consistent with EHCI
>   fotg210: Remove superfluous macro definitions
>   fotg210: Remove duplicate ehci-dbgp declarations
>   fotg210: Use ehci_dbg_port struct
>   usb: Remove __init from early_dbgp_init() prototype
> 
>  drivers/usb/host/fotg210.h    | 62 ++------------------------------
>  drivers/usb/host/fusbh200.h   | 62 ++------------------------------
>  include/linux/usb/ehci-dbgp.h | 83 +++++++++++++++++++++++++++++++++++++++++++
>  include/linux/usb/ehci_def.h  | 65 ++-------------------------------
>  4 files changed, 91 insertions(+), 181 deletions(-)
>  create mode 100644 include/linux/usb/ehci-dbgp.h

It deletes lines of code overall, which looks good to me.  Feel free to
resend without the "RFC" and I will queue it up.

thanks,

greg k-h

  parent reply	other threads:[~2014-11-03 23:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  3:07 [RFC RESEND 00/10] Create separate header for ehci-dbgp driver Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 01/10] usb: Create separate header for ehci-dbgp Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 02/10] fusbh200: Make Xen notificaiton consistent with EHCI Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 03/10] fusbh200: Remove superfluous macro definitions Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 04/10] fusbh200: Remove duplicate ehci-dbgp declarations Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 05/10] fusbh200: Use ehci_dbg_port struct Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 06/10] fotg210: Make Xen notificaiton consistent with EHCI Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 07/10] fotg210: Remove superfluous macro definitions Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 08/10] fotg210: Remove duplicate ehci-dbgp declarations Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 09/10] fotg210: Use ehci_dbg_port struct Chris Rorvick
2014-11-03  3:07 ` [RFC RESEND 10/10] usb: Remove __init from early_dbgp_init() prototype Chris Rorvick
2014-11-03 23:09 ` Greg Kroah-Hartman [this message]
2014-11-05  1:44   ` [RFC RESEND 00/10] Create separate header for ehci-dbgp driver Chris Rorvick
2014-11-04  8:46 ` Daniele Forsi
  -- strict thread matches above, loose matches on Subject: below --
2014-09-29  4:48 Chris Rorvick

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=20141103230913.GA11259@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris@rorvick.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=stern@rowland.harvard.edu \
    /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.