lkml.org 
[lkml]   [2023]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [GIT PULL]: Generic phy updates for v6.4
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

\
 
 \ /
  Last update: 2023-05-04 20:01    [W:0.044 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site