All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Roger Quadros <rogerq@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [usb-next, v2 PATCH] usb: xhci: skip phys initialization of shared hcd
Date: Thu, 22 Mar 2018 10:01:27 +0100	[thread overview]
Message-ID: <20180322090127.GA12048@kroah.com> (raw)
In-Reply-To: <643701fef843f91931e3a68779afe053c63c96f6.1521707846.git.chunfeng.yun@mediatek.com>

On Thu, Mar 22, 2018 at 04:39:20PM +0800, Chunfeng Yun wrote:
> The phys has already been initialized when add primary hcd,
> including usb2 phys and usb3 phys also if exist, so needn't
> re-parse "phys" property again.
> 
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
>  drivers/usb/core/hcd.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

What changed from version 1?

Always put that below the --- line like the kernel documentation asks
you to do.

v3?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Roger Quadros <rogerq@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
	linux-mediatek@lists.infradead.org
Subject: [usb-next,v2] usb: xhci: skip phys initialization of shared hcd
Date: Thu, 22 Mar 2018 10:01:27 +0100	[thread overview]
Message-ID: <20180322090127.GA12048@kroah.com> (raw)

On Thu, Mar 22, 2018 at 04:39:20PM +0800, Chunfeng Yun wrote:
> The phys has already been initialized when add primary hcd,
> including usb2 phys and usb3 phys also if exist, so needn't
> re-parse "phys" property again.
> 
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
>  drivers/usb/core/hcd.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

What changed from version 1?

Always put that below the --- line like the kernel documentation asks
you to do.

v3?

thanks,

greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [usb-next, v2 PATCH] usb: xhci: skip phys initialization of shared hcd
Date: Thu, 22 Mar 2018 10:01:27 +0100	[thread overview]
Message-ID: <20180322090127.GA12048@kroah.com> (raw)
In-Reply-To: <643701fef843f91931e3a68779afe053c63c96f6.1521707846.git.chunfeng.yun@mediatek.com>

On Thu, Mar 22, 2018 at 04:39:20PM +0800, Chunfeng Yun wrote:
> The phys has already been initialized when add primary hcd,
> including usb2 phys and usb3 phys also if exist, so needn't
> re-parse "phys" property again.
> 
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
>  drivers/usb/core/hcd.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

What changed from version 1?

Always put that below the --- line like the kernel documentation asks
you to do.

v3?

thanks,

greg k-h

  reply	other threads:[~2018-03-22  9:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  8:39 [usb-next, v2 PATCH] usb: xhci: skip phys initialization of shared hcd Chunfeng Yun
2018-03-22  8:39 ` Chunfeng Yun
2018-03-22  8:39 ` Chunfeng Yun
2018-03-22  8:39 ` [usb-next,v2] " Chunfeng Yun
2018-03-22  9:01 ` Greg Kroah-Hartman [this message]
2018-03-22  9:01   ` [usb-next, v2 PATCH] " Greg Kroah-Hartman
2018-03-22  9:01   ` [usb-next,v2] " Greg Kroah-Hartman
2018-03-22  9:21   ` [usb-next, v2 PATCH] " Chunfeng Yun
2018-03-22  9:21     ` Chunfeng Yun
2018-03-22  9:21     ` Chunfeng Yun
2018-03-22  9:21     ` [usb-next,v2] " Chunfeng Yun
2018-03-22 12:00     ` [usb-next, v2 PATCH] " Greg Kroah-Hartman
2018-03-22 12:00       ` Greg Kroah-Hartman
2018-03-22 12:00       ` [usb-next,v2] " Greg Kroah-Hartman
2018-03-22 12:29 ` [usb-next, v3 PATCH] " Roger Quadros
2018-03-22 12:29   ` Roger Quadros
2018-03-22 12:29   ` Roger Quadros
2018-03-22 12:29   ` [usb-next,v2] " Roger Quadros
2018-03-22 12:53 ` [usb-next, v3 PATCH] " Greg Kroah-Hartman
2018-03-22 12:53   ` Greg Kroah-Hartman
2018-03-22 12:53   ` [usb-next,v2] " Greg Kroah-Hartman
2018-03-23  3:20   ` [usb-next, v3 PATCH] " Chunfeng Yun
2018-03-23  3:20     ` Chunfeng Yun
2018-03-23  3:20     ` Chunfeng Yun
2018-03-23  3:20     ` [usb-next,v2] " Chunfeng Yun

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=20180322090127.GA12048@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chunfeng.yun@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=mathias.nyman@intel.com \
    --cc=matthias.bgg@gmail.com \
    --cc=rogerq@ti.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.