From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Hesselbarth Subject: Re: [PATCH v5 00/13] net: mv643xx_eth DT support and fixes Date: Fri, 31 May 2013 08:28:58 +0200 Message-ID: <51A8432A.4000602@gmail.com> References: <1369154510-4927-1-git-send-email-sebastian.hesselbarth@gmail.com> <1369855975-21489-1-git-send-email-sebastian.hesselbarth@gmail.com> <20130530.175549.407800685811475192.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: buytenh@wantstofly.org, jason@lakedaemon.net, andrew@lunn.ch, benh@kernel.crashing.org, netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org To: David Miller Return-path: In-Reply-To: <20130530.175549.407800685811475192.davem@davemloft.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 05/31/2013 02:55 AM, David Miller wrote: > From: Sebastian Hesselbarth > Date: Wed, 29 May 2013 21:32:42 +0200 > >> For the patches above I suggest to take Patches 1-6 through David >> Miller's branch, and Patches 7-12 through Jason Cooper's when the >> former have appeared on mainline linux. The patch set has been based >> on v3.10-rc3. > > Patches 1-6 applied to net-next, and patch #1 queued up for -stable. David, thanks for pulling these in. I finally found how to check if a patch already went into -stable. As Jason already said, the mdio patch that #1 fixes did not yet went into -stable. Can you unqueue it? Sorry for the confusion. Sebastian