From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"kernel test robot" <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: [stable:linux-5.15.y 1642/9999] ERROR: Input tree has errors, aborting (use -f to force output)
Date: Sun, 15 Jan 2023 15:14:27 +0100 [thread overview]
Message-ID: <Y8QKQ1XKEZvtmJYc@kroah.com> (raw)
In-Reply-To: <CAMhs-H_fykbcZjSQ0LKOmtWMLjekDgUHsJjNNqSvYvbY=wbkHQ@mail.gmail.com>
On Sun, Jan 15, 2023 at 01:52:58PM +0100, Sergio Paracuellos wrote:
> On Sun, Jan 15, 2023 at 10:05 AM Arınç ÜNAL <arinc.unal@arinc9.com> wrote:
> >
> > Sergio, this issue hasn't seem to gone away. If you haven't sent the
> > patch you mentioned here [1], I think Greg taking your upstream commit
> > [2] to 5.15.y tree would be the easiest solution.
> >
> > [1]:
> > https://lore.kernel.org/all/CAMhs-H8BLheXBc+BcDH_PKmDg+_bWF9OmiS_grw1mO+RxW+J8Q@mail.gmail.com/
> > [2]:
> > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/staging/mt7621-dts/mt7621.dtsi?id=ce835dbd04d7b24f9fd50d9a9c59be46304aaa8a
>
> I forgot I sent [2] at some point :). Yes, taking directly that patch
> sounds easier.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2023-01-15 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 1:12 [stable:linux-5.15.y 1642/9999] ERROR: Input tree has errors, aborting (use -f to force output) kernel test robot
2023-01-15 9:04 ` Arınç ÜNAL
2023-01-15 12:52 ` Sergio Paracuellos
2023-01-15 14:14 ` Greg Kroah-Hartman [this message]
2023-01-15 20:09 ` Arınç ÜNAL
2023-01-16 6:14 ` Sergio Paracuellos
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=Y8QKQ1XKEZvtmJYc@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arinc.unal@arinc9.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=sergio.paracuellos@gmail.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