All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Michal Simek <michal.simek@xilinx.com>,
	Manish Narani <manish.narani@xilinx.com>
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org, balbi@kernel.org,
	p.zabel@pengutronix.de, git@xilinx.com,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] usb: dwc3: Add driver for Xilinx platforms
Date: Sun, 11 Apr 2021 07:02:12 -0700	[thread overview]
Message-ID: <82dc676c-10c7-2a45-7ab3-ecad46eab0a3@roeck-us.net> (raw)
In-Reply-To: <ee280235-736d-1689-d324-b090c21106c9@xilinx.com>

Michal,

On 4/7/21 11:08 PM, Michal Simek wrote:
...
> It looks like that you directly created the patch. Isn't it better to
> send it yourself? Or do you want Manish to create it based on guidance
> above?
> 
-next is substantially broken all over the place. I already spend way too much
time bisecting and analyzing the failures, and making sure that the problems
are not caused by qemu (which is why I tracked down this problem in such detail).
I don't really have time to write patches and guide them through the process,
sorry.

Guenter

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Michal Simek <michal.simek@xilinx.com>,
	Manish Narani <manish.narani@xilinx.com>
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org, balbi@kernel.org,
	p.zabel@pengutronix.de, git@xilinx.com,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] usb: dwc3: Add driver for Xilinx platforms
Date: Sun, 11 Apr 2021 07:02:12 -0700	[thread overview]
Message-ID: <82dc676c-10c7-2a45-7ab3-ecad46eab0a3@roeck-us.net> (raw)
In-Reply-To: <ee280235-736d-1689-d324-b090c21106c9@xilinx.com>

Michal,

On 4/7/21 11:08 PM, Michal Simek wrote:
...
> It looks like that you directly created the patch. Isn't it better to
> send it yourself? Or do you want Manish to create it based on guidance
> above?
> 
-next is substantially broken all over the place. I already spend way too much
time bisecting and analyzing the failures, and making sure that the problems
are not caused by qemu (which is why I tracked down this problem in such detail).
I don't really have time to write patches and guide them through the process,
sorry.

Guenter

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-04-11 14:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  6:52 [PATCH v4 0/2] Add a separate DWC3 OF driver for Xilinx platforms Manish Narani
2021-03-17  6:52 ` Manish Narani
2021-03-17  6:52 ` [PATCH v4 1/2] dt-bindings: usb: dwc3-xilinx: Add documentation for Versal DWC3 Controller Manish Narani
2021-03-17  6:52   ` Manish Narani
2021-03-17  6:52 ` [PATCH v4 2/2] usb: dwc3: Add driver for Xilinx platforms Manish Narani
2021-03-17  6:52   ` Manish Narani
2021-03-17  9:50   ` kernel test robot
2021-03-17  9:50     ` kernel test robot
2021-03-23 11:47     ` Greg KH
2021-03-23 11:47       ` Greg KH
2021-03-23 11:47       ` Greg KH
2021-03-24  9:16       ` Rong Chen
2021-03-24  9:16         ` Rong Chen
2021-03-24  9:16         ` Rong Chen
2021-04-07 21:48   ` Guenter Roeck
2021-04-07 21:48     ` Guenter Roeck
2021-04-08  6:08     ` Michal Simek
2021-04-08  6:08       ` Michal Simek
     [not found]       ` <a7bbf265-a771-2c2e-b5e7-a189692ca280@hoefle.co>
2021-04-08 19:11         ` Marco Hoefle
2021-04-11 14:02       ` Guenter Roeck [this message]
2021-04-11 14:02         ` Guenter Roeck
2021-04-12  8:01         ` Michal Simek
2021-04-12  8:01           ` Michal Simek

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=82dc676c-10c7-2a45-7ab3-ecad46eab0a3@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=balbi@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=manish.narani@xilinx.com \
    --cc=michal.simek@xilinx.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@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.