Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <ZFI74eeUzVPKhi4f@matsya> <20230504150624.GA1000378@dev-arch.thelio-3990X>
 <ZFPPucb9VNLB8r8v@matsya>
In-Reply-To: <ZFPPucb9VNLB8r8v@matsya>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu, 4 May 2023 10:23:51 -0700
Message-ID: <CAHk-=wi-ve0h02vsNrzuox58rLXSbzcjay+k=XnUueWRh6cO2Q@mail.gmail.com>
Subject: Re: [GIT PULL]: Generic phy updates for v6.4
To:     Vinod Koul <vkoul@kernel.org>
Cc:     Nathan Chancellor <nathan@kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux Phy <linux-phy@lists.infradead.org>,
        Nick Desaulniers <ndesaulniers@google.com>,
        llvm@lists.linux.dev
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Thu, May 4, 2023 at 8:31=E2=80=AFAM Vinod Koul <vkoul@kernel.org> wrote:
> Sorry between vacation and travel, this was missed.
>
> No worries we have process to deal with this, so this shall go in as
> fixes.. I will do the needful shortly

You need to do it *now*.

You should never have sent the pull request to me in the first place
if you hadn't checked the status in linux-next.

The point of linux-next is to find failures. And if you don't then
*care* about the failures, then it has all become  entirely pointless,
and it's effectively the same as if it had never been there in the
first place.

So this needs to get fixed *PRONTO*, and it needs to never ever happen agai=
n.

Because if it does happen, I will consider your code to effectively
never have been in linux-next, and thus just not be an option for
pulling.

This isn't debatable. You don't put things in linux-next, ignore the
reports, and then send things upstream anyway.

If you don't have time to check the status of your tree in linux-next,
you don't have the time to do a pull request. That's just how it
works.

                      Linus