From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Yu Tu <yu.tu@amlogic.com>,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
kernel test robot <lkp@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH V3] tty: serial: meson: Fix the compile link error reported by kernel test robot
Date: Mon, 28 Feb 2022 22:21:50 +0100 [thread overview]
Message-ID: <Yh087tJhakKHs88e@kroah.com> (raw)
In-Reply-To: <29b34655-f820-39c9-4363-878481cd3f63@baylibre.com>
On Mon, Feb 28, 2022 at 03:13:48PM +0100, Neil Armstrong wrote:
> Hi,
>
> On 28/02/2022 14:55, Yu Tu wrote:
> > Describes the calculation of the UART baud rate clock using a clock
> > frame. Forgot to add in Kconfig kernel test Robot compilation error
> > due to COMMON_CLK dependency.
> >
> > Fixes: ("tty: serial:meson: Describes the calculation of the UART baud rate clock using a clock frame“)
>
> As I already replied on V2 of this patch, you're invited to apply these fixes directly
> on the next version of your "Use CCF to describe the UART baud rate clock" patchset
> and not as a separate patch.
No, this is broken in linux-next now as the path listed here is in my
tree right now.
I need a fix for it, or I can revert the original.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-28 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:55 [PATCH V3] tty: serial: meson: Fix the compile link error reported by kernel test robot Yu Tu
2022-02-28 14:13 ` Neil Armstrong
2022-02-28 14:36 ` Yu Tu
2022-02-28 21:21 ` Greg Kroah-Hartman [this message]
2022-03-01 7:23 ` Neil Armstrong
2022-03-01 7:47 ` Yu Tu
2022-03-01 8:33 ` Jerome Brunet
2022-03-01 21:06 ` Greg Kroah-Hartman
2022-03-03 8:09 ` Neil Armstrong
2022-02-28 14:27 ` Dan Carpenter
2022-02-28 21:23 ` Greg Kroah-Hartman
2022-03-01 2:43 ` Yu Tu
-- strict thread matches above, loose matches on Subject: below --
2022-03-01 5:33 Yu Tu
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=Yh087tJhakKHs88e@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=jbrunet@baylibre.com \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=yu.tu@amlogic.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 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).