All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rui Miguel Silva" <rui.silva@linaro.org>
To: "Dietmar Eggemann" <dietmar.eggemann@arm.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 0/5] usb: isp1760: arm tc2 board isp1761 fixes
Date: Fri, 27 Aug 2021 14:03:29 +0100	[thread overview]
Message-ID: <CDUBDOZHL5NC.2DP7OD0R936NH@arch-thunder> (raw)
In-Reply-To: <f9f1ceb6-6db5-8ef1-944d-381bdf65599a@arm.com>

Hi  Dietmar,
On Fri Aug 27, 2021 at 12:15 PM WEST, Dietmar Eggemann wrote:

> - deggeman@gmx.de
> + dietmar.eggemann@arm.com
>
> On 27/08/2021 10:21, Rui Miguel Silva wrote:
> > Hi,
> > Dietmar complained that the latest changes to this driver
> > broke booting his Arm TC2 board [0]. I did not have one of
> > that boards but Dietmar provided out of band help trying to
> > debug the issue, many thanks for that.
> > 
> > Meanwhile, yesterday I could get access (remotely) to one of
> > TC2 board and manage to fix the issues that were breaking
> > this to work on that system.
> > 
> > This is rebased on top of the latest (this evening)
> > usb-testing/(this morning) usb-next. If, and I am sure it is
> > too late to include in to 5.14, it should go to the first
> > 5.14.y stable with this tag:
> > 
> > Fixes: 1da9e1c06873 ("usb: isp1760: move to regmap for register access")
> > 
> > Thanks again Dietmar for reporting and your help.
> > 
> > Cheers,
> >   Rui
> > 
> > [0]: https://lore.kernel.org/linux-usb/11ed5458-4b88-ad72-4497-89ff9346a40b@gmx.de/
> > 
> > Rui Miguel Silva (5):
> >   usb: isp1760: fix memory pool initialization
> >   usb: isp1760: fix qtd fill length
> >   usb: isp1760: write to status and address register
> >   usb: isp1760: use the right irq status bit
> >   usb: isp1760: otg control register access
> > 
> >  drivers/usb/isp1760/isp1760-core.c | 50 ++++++++++++++++--------------
> >  drivers/usb/isp1760/isp1760-hcd.c  | 33 ++++++++++----------
> >  drivers/usb/isp1760/isp1760-regs.h | 16 ++++++++++
> >  drivers/usb/isp1760/isp1760-udc.c  | 12 +++----
> >  4 files changed, 65 insertions(+), 46 deletions(-)
>
> Works fine on my TC2 too. Thanks!
>
> Tested-by: Dietmar Eggemann <dietmar.eggemann@arm.com>

Great, ...
>
> Maybe you can change as well to:
>
> Reported-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
>
> I used the wrong email address last week.

Ok, I will spin a V2 with the test tag and with the email changed.
Thanks for your time.

Cheers,
  Rui




      reply	other threads:[~2021-08-27 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27  8:21 [PATCH 0/5] usb: isp1760: arm tc2 board isp1761 fixes Rui Miguel Silva
2021-08-27  8:21 ` [PATCH 1/5] usb: isp1760: fix memory pool initialization Rui Miguel Silva
2021-08-27  8:21 ` [PATCH 2/5] usb: isp1760: fix qtd fill length Rui Miguel Silva
2021-08-27  8:21 ` [PATCH 3/5] usb: isp1760: write to status and address register Rui Miguel Silva
2021-08-27  8:21 ` [PATCH 4/5] usb: isp1760: use the right irq status bit Rui Miguel Silva
2021-08-27  8:21 ` [PATCH 5/5] usb: isp1760: otg control register access Rui Miguel Silva
2021-08-27 11:15 ` [PATCH 0/5] usb: isp1760: arm tc2 board isp1761 fixes Dietmar Eggemann
2021-08-27 13:03   ` Rui Miguel Silva [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=CDUBDOZHL5NC.2DP7OD0R936NH@arch-thunder \
    --to=rui.silva@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@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.