Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <92cc6617-e2c3-e3b8-cf20-c8ccf748d37a@monstr.eu>
 <CAHk-=wiFMsSnjERZno13XbTF6m3pk2beAH5R-9RGct7hXzG3ig@mail.gmail.com> <f2b951c9-f904-58d7-0634-0a0d42f71066@monstr.eu>
In-Reply-To: <f2b951c9-f904-58d7-0634-0a0d42f71066@monstr.eu>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue, 4 Feb 2020 22:04:25 +0000
Message-ID: <CAHk-=wj1xRXSKMPt-y=A6-nUqDQQwK2eHHfF96zdk0bWkfUCzQ@mail.gmail.com>
Subject: Re: [GIT PULL] arch/microblaze patches for 5.6-rc1
To:     Michal Simek <monstr@monstr.eu>
Cc:     LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Feb 4, 2020 at 5:37 PM Michal Simek <monstr@monstr.eu> wrote:
>
> Sorry about it. All that patches has been sent and done till the mid of
> January. Some of them even earlier.
> I just needed to remove one patch from queue which we found is causing
> the issue. That's why instead of revert I completely remove it and
> rebase the rest of the tree.
> I will handle that differently next time.

Note that if this happens again, and you have a really good reason to
rebase, please _mention_ that reason.

The whole taking me by surprise when I notice after-the-fact that I've
pulled something that was committed just hours before is about the
worst thing that can happen (always excepting obviously untested code
- me finding that the code doesn't even compile is even worse, of
course, even if it wasn't recently committed).

So if there's a good reason why something is very recent, and you
mention it, and it's not a common pattern, I get much less upset.

              Linus