From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752716AbbJFNJ2 (ORCPT ); Tue, 6 Oct 2015 09:09:28 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:46765 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460AbbJFNJ1 (ORCPT ); Tue, 6 Oct 2015 09:09:27 -0400 Date: Tue, 06 Oct 2015 06:25:08 -0700 (PDT) Message-Id: <20151006.062508.168154086334967576.davem@davemloft.net> To: jonringle@gmail.com Cc: broonie@kernel.org, jon@ringle.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jringle@gridpoint.com Subject: Re: [PATCH 1/2] regmap: only call custom reg_update_bits() if reg is marked volatile From: David Miller In-Reply-To: References: <20151005.232956.105884641412802470.davem@davemloft.net> <20151006101305.GG12635@sirena.org.uk> X-Mailer: Mew version 6.4 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 06 Oct 2015 06:09:26 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jon Ringle Date: Tue, 6 Oct 2015 08:50:43 -0400 > 4) David should then merge the regmap for-next branch into net-next Nope, this doesn't work at all. It is my tree which people depend upon, not the other way around.