From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-usb@vger.kernel.org, linux-mips@vger.kernel.org,
lkft-triage@lists.linaro.org, Thinh.Nguyen@synopsys.com,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH] usb: dwc3: dwc3-octeon: Verify clock divider
Date: Tue, 8 Aug 2023 12:00:42 +0200 [thread overview]
Message-ID: <2023080830-wincing-goldmine-def9@gregkh> (raw)
In-Reply-To: <ZNIM7tlBNdHFzXZG@lenoch>
On Tue, Aug 08, 2023 at 11:37:50AM +0200, Ladislav Michl wrote:
> From: Ladislav Michl <ladis@linux-mips.org>
>
> Although valid USB clock divider will be calculated for all valid
> Octeon core frequencies, make code formally correct limiting
> divider not to be greater that 7 so it fits into H_CLKDIV_SEL
> field.
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> Closes: https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230808/testrun/18882876/suite/build/test/gcc-8-cavium_octeon_defconfig/log
> ---
> Greg, if you want to resent whole serie, just drop me a note.
> Otherwise, this patch is meant to be applied on to of it.
On top of what series?
confused,
greg k-h
next prev parent reply other threads:[~2023-08-08 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:37 [PATCH] usb: dwc3: dwc3-octeon: Verify clock divider Ladislav Michl
2023-08-08 10:00 ` Greg Kroah-Hartman [this message]
2023-08-08 10:38 ` Ladislav Michl
2023-08-08 10:45 ` Greg Kroah-Hartman
2023-08-08 23:41 ` Thinh Nguyen
2023-08-10 9:00 ` Philippe Mathieu-Daudé
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=2023080830-wincing-goldmine-def9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=oss-lists@triops.cz \
--cc=tsbogend@alpha.franken.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).