All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
Cc: Grigor Tovmasyan <Grigor.Tovmasyan@synopsys.com>,
	John Youn <John.Youn@synopsys.com>,
	Felipe Balbi <balbi@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Gevorg Sahakyan <Gevorg.Sahakyan@synopsys.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: [v3,03/49] usb: dwc2: Remove version check in GSNPSID
Date: Sat, 30 Dec 2017 15:11:59 +0100	[thread overview]
Message-ID: <20171230141159.GA8431@kroah.com> (raw)

On Fri, Dec 29, 2017 at 07:56:18PM +0000, Minas Harutyunyan wrote:
> Hi Greg,
> 
> On 12/29/2017 8:59 PM, Greg KH wrote:
> > On Tue, Dec 26, 2017 at 03:22:05PM +0400, Grigor Tovmasyan wrote:
> >> From: Gevorg Sahakyan <sahakyan@synopsys.com>
> >>
> >> Only check the ID portion of the GSNPSID register and don’t check
> >> the version. This will allow the driver to work with version 4.00a
> >> and later of the DWC_hsotg IP.
> >>
> >> Cc: stable@vger.kernel.org
> > 
> > For bugfixes like this, or other stable patches, they should all be
> > first in the series, so that none of them depened on any previous
> > patches.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> 1. Mentioned patch submitted to lkml as alone patch on Dec 6 by Gevorg 
> Sahakyan but was ignored by community.

lkml is not where to send dwc patches, you know better than that :)

That's what scripts/get_maintainer.pl is for, always use that.

> 2. This patch not dependent on any other previous patches in series.

How are we supposed to know that?  For stuff like this that are bug
fixes and for stable kernels, they should be in a separate series so we
can apply them to the latest -rc release, all of the cleanups and new
features should be in a separate patch series.

Anyway, as others said, 49 patches is a lot, let's wait for the
maintainers to return from vacation before anything else...

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: Greg KH <gregkh@linuxfoundation.org>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
Cc: Grigor Tovmasyan <Grigor.Tovmasyan@synopsys.com>,
	John Youn <John.Youn@synopsys.com>,
	Felipe Balbi <balbi@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Gevorg Sahakyan <Gevorg.Sahakyan@synopsys.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v3 03/49] usb: dwc2: Remove version check in GSNPSID
Date: Sat, 30 Dec 2017 15:11:59 +0100	[thread overview]
Message-ID: <20171230141159.GA8431@kroah.com> (raw)
In-Reply-To: <410670D7E743164D87FA6160E7907A560113A53D12@am04wembxa.internal.synopsys.com>

On Fri, Dec 29, 2017 at 07:56:18PM +0000, Minas Harutyunyan wrote:
> Hi Greg,
> 
> On 12/29/2017 8:59 PM, Greg KH wrote:
> > On Tue, Dec 26, 2017 at 03:22:05PM +0400, Grigor Tovmasyan wrote:
> >> From: Gevorg Sahakyan <sahakyan@synopsys.com>
> >>
> >> Only check the ID portion of the GSNPSID register and don’t check
> >> the version. This will allow the driver to work with version 4.00a
> >> and later of the DWC_hsotg IP.
> >>
> >> Cc: stable@vger.kernel.org
> > 
> > For bugfixes like this, or other stable patches, they should all be
> > first in the series, so that none of them depened on any previous
> > patches.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> 1. Mentioned patch submitted to lkml as alone patch on Dec 6 by Gevorg 
> Sahakyan but was ignored by community.

lkml is not where to send dwc patches, you know better than that :)

That's what scripts/get_maintainer.pl is for, always use that.

> 2. This patch not dependent on any other previous patches in series.

How are we supposed to know that?  For stuff like this that are bug
fixes and for stable kernels, they should be in a separate series so we
can apply them to the latest -rc release, all of the cleanups and new
features should be in a separate patch series.

Anyway, as others said, 49 patches is a lot, let's wait for the
maintainers to return from vacation before anything else...

thanks,

greg k-h

             reply	other threads:[~2017-12-30 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-30 14:11 Greg Kroah-Hartman [this message]
2017-12-30 14:11 ` [PATCH v3 03/49] usb: dwc2: Remove version check in GSNPSID Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2018-01-08 12:13 [v3,03/49] " Grigor Tovmasyan
2018-01-08 12:13 ` [PATCH v3 03/49] " Grigor Tovmasyan
2017-12-29 19:56 [v3,03/49] " Minas Harutyunyan
2017-12-29 19:56 ` [PATCH v3 03/49] " Minas Harutyunyan
2017-12-29 16:59 [v3,03/49] " Greg Kroah-Hartman
2017-12-29 16:59 ` [PATCH v3 03/49] " Greg KH
2017-12-26 11:22 [v3,03/49] " Grigor Tovmasyan
2017-12-26 11:22 ` [PATCH v3 03/49] " Grigor Tovmasyan

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=20171230141159.GA8431@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Gevorg.Sahakyan@synopsys.com \
    --cc=Grigor.Tovmasyan@synopsys.com \
    --cc=John.Youn@synopsys.com \
    --cc=Minas.Harutyunyan@synopsys.com \
    --cc=balbi@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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.