From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Bin Liu <b-liu@ti.com>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Andreas Kemnade <andreas@kemnade.info>,
Bhushan Shah <bshah@kde.org>, Drew Fustini <drew@beagleboard.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 1/2] usb: musb: Simplify cable state handling
Date: Mon, 14 Jun 2021 10:26:21 +0200 [thread overview]
Message-ID: <YMcSrUXLZxaQM6St@kroah.com> (raw)
In-Reply-To: <YMLx9O0DnWc1umPo@atomide.com>
On Fri, Jun 11, 2021 at 08:17:40AM +0300, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [210609 12:00]:
> > * Greg Kroah-Hartman <gregkh@linuxfoundation.org> [210609 09:26]:
> > > On Fri, Jun 04, 2021 at 11:05:35AM +0300, Tony Lindgren wrote:
> > > > Simplify cable state handling a bit to leave out duplicated code.
> > > > We are just scheduling work and showing state info if a recheck is
> > > > needed. No intended functional changes.
> > > >
> > > > Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
> > > > Cc: Andreas Kemnade <andreas@kemnade.info>
> > > > Cc: Bhushan Shah <bshah@kde.org>
> > > > Cc: Drew Fustini <drew@beagleboard.org>
> > > > Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> > > > Signed-off-by: Tony Lindgren <tony@atomide.com>
> > > > ---
> > > > drivers/usb/musb/musb_core.c | 40 ++++++++++++++++++------------------
> > > > 1 file changed, 20 insertions(+), 20 deletions(-)
> > >
> > > Does not apply to my usb-next branch, what tree/branch did you make this
> > > against?
> >
> > This was against Linux next last week, I'll take a look and
> > repost.
>
> Looks like the issue applying these patches is caused by commit
> b65ba0c362be ("usb: musb: fix MUSB_QUIRK_B_DISCONNECT_99 handling")
> that is in usb-linus but not in usb-next.
>
> Probably best to merge usb-linus to usb-next and then these patches
> apply no problem and a merge conflict is avoided?
>
> Let me know if you still want me to repost against usb-next, I can
> do that no problem if you prefer that :)
Now that I have merged usb-linus into usb-next, I can take these,
thanks.
greg k-h
prev parent reply other threads:[~2021-06-14 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 8:05 [PATCH 1/2] usb: musb: Simplify cable state handling Tony Lindgren
2021-06-04 8:05 ` [PATCH 2/2] usb: musb: Implement tracing for state change events Tony Lindgren
2021-06-09 9:26 ` [PATCH 1/2] usb: musb: Simplify cable state handling Greg Kroah-Hartman
2021-06-09 12:00 ` Tony Lindgren
2021-06-11 5:17 ` Tony Lindgren
2021-06-14 8:26 ` Greg Kroah-Hartman [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=YMcSrUXLZxaQM6St@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andreas@kemnade.info \
--cc=b-liu@ti.com \
--cc=bshah@kde.org \
--cc=drew@beagleboard.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tony@atomide.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.