From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.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
Subject: Re: [GIT PULL]: Generic phy updates for v6.4
Date: Thu, 4 May 2023 23:30:34 +0530 [thread overview]
Message-ID: <ZFPywqdpgESLD46Z@matsya> (raw)
In-Reply-To: <CAHk-=wi-ve0h02vsNrzuox58rLXSbzcjay+k=XnUueWRh6cO2Q@mail.gmail.com>
On 04-05-23, 10:23, Linus Torvalds wrote:
> On Thu, May 4, 2023 at 8:31 AM 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*.
It was already done a bit ago and applied to my fixes and should be in
-next tomorrow. I will wait a day before sending you fixes update.
> 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 again.
Ack, agree I should have paid it more attention. Between vacation and
travel and stuff I have missed it this time, will ensure this doesn't
happen again.
>
> 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
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2023-05-04 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 10:48 [GIT PULL]: Generic phy updates for v6.4 Vinod Koul
2023-05-03 18:32 ` pr-tracker-bot
2023-05-04 15:06 ` Nathan Chancellor
2023-05-04 15:31 ` Vinod Koul
2023-05-04 17:23 ` Linus Torvalds
2023-05-04 18:00 ` Vinod Koul [this message]
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=ZFPywqdpgESLD46Z@matsya \
--to=vkoul@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=torvalds@linux-foundation.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 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).