From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jonathan Corbet <corbet@lwn.net>
Subject: Re: linux-next: manual merge of the jc_docs tree with the kbuild
 tree
Date: Mon, 3 Jul 2017 12:13:32 -0600
Message-ID: <20170703121332.2f0d43b5@lwn.net>
References: <20170626111331.5443587b@canb.auug.org.au>
        <20170703125859.0678914b@canb.auug.org.au>
        <054dc72a-39ce-ee8c-62d1-c17f487009de@gmx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Return-path: <linux-next-owner@vger.kernel.org>
Received: from ms.lwn.net ([45.79.88.28]:48920 "EHLO ms.lwn.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1754208AbdGCSNf (ORCPT <rfc822;linux-next@vger.kernel.org>);
        Mon, 3 Jul 2017 14:13:35 -0400
In-Reply-To: <054dc72a-39ce-ee8c-62d1-c17f487009de@gmx.com>
Sender: linux-next-owner@vger.kernel.org
List-ID: <linux-next.vger.kernel.org>
To: Kamil Rytarowski <n54@gmx.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Masahiro Yamada <yamada.masahiro@socionext.com>, Linux-Next Mailing List <linux-next@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>

On Mon, 3 Jul 2017 18:43:32 +0200
Kamil Rytarowski <n54@gmx.com> wrote:

> Am I expected to do it myself and resend a new patch?
> 
No, there should be no need for that.  I've already mentioned the issue
in my pull request; if the same happens on the kbuild side, Linus will
not have a hard time figuring out what to do.

jon