From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2300DC43603 for ; Thu, 19 Dec 2019 10:59:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E886B24650 for ; Thu, 19 Dec 2019 10:59:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=bgdev-pl.20150623.gappssmtp.com header.i=@bgdev-pl.20150623.gappssmtp.com header.b="it61dloB" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726652AbfLSK7l (ORCPT ); Thu, 19 Dec 2019 05:59:41 -0500 Received: from mail-il1-f194.google.com ([209.85.166.194]:42023 "EHLO mail-il1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726696AbfLSK7l (ORCPT ); Thu, 19 Dec 2019 05:59:41 -0500 Received: by mail-il1-f194.google.com with SMTP id a6so4482175ili.9 for ; Thu, 19 Dec 2019 02:59:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=YEnz6rtmOsqvmaj2aduLHDl66N+lt0mfLf6uw+pTiDQ=; b=it61dloBhcSk7XfxC33/CGeJ+D3J3nOc7Y/y6UWUpck1kTpT2JgJrOEebHC97Rb9b9 0+zPbW0SW6LJJvlQv1+92dgCo+CAfpS9gElWv0kCnTplCvQ53jYHfc3hHWOzOfJcEqNp KfHSTmkjktmk3oqCC6L/zFjDBJnrxvScUP/VDcIGwPrwXnZakb+UU2anfDVb0jHxZxpr OgP7ja80QFqG65VQhBzdd2hlsaEtw9OJk9TqdroTkzSNPaeLRplqM8IXX7oE7O3VrNv6 xlyDMxnDBzkXqjQBsxU4pgo+WknYG3ilEMSxYDlMWxrFg6zzJTloTVkGaJuOzz28RgOj nqWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=YEnz6rtmOsqvmaj2aduLHDl66N+lt0mfLf6uw+pTiDQ=; b=P7wotofzArlWSChm+uUAI5z3gF4XVgvond5R7SamtGXKHASdtRgylQ15/wFdNC9j0t CsL5rv0n44qIHZrHFLVz7OTeOLBIZofZWaxgDiaRvQr+rqrR/vb3033ouWTSZmQYCmeG 9fesFAWzTeCEiu0qWuvTN0hr3GR65YeX7Hv59F09P0qVfnhQ3Ehv6JZlBslpQdNUF7Cb pDkp6y1IUtGurc0eCYQ9RYeMnt2TlKQEOodNHi5VQBP7WRauZQEnbHOrcQx3JCLP4W4O 9rG9k8Os7ABqyZ6dtdOjRCLwrkXvOevXtnx94hvcxb0cPFicD/N0QnAm1qzfTFBlrZV5 zs8Q== X-Gm-Message-State: APjAAAVZoCKMKcRpgazest0xG/zdFnk74Hf/md28/K5VrFq82fvtxiHp jck/Aa/dn51IMarNDRp4qxMneByZ76QvEqdlEh9ghQ== X-Google-Smtp-Source: APXvYqz+lUlue15W96AqQpyFaKFQAt4AOaLfE1iA5SmiiXn2rwdF7Mivdq3SM/UWgXrCxbg1MQ7kOSBxmwYZlVVsric= X-Received: by 2002:a92:9c04:: with SMTP id h4mr6772212ili.6.1576753180511; Thu, 19 Dec 2019 02:59:40 -0800 (PST) MIME-Version: 1.0 References: <20191210154157.21930-1-ktouil@baylibre.com> In-Reply-To: From: Bartosz Golaszewski Date: Thu, 19 Dec 2019 11:59:29 +0100 Message-ID: Subject: Re: [PATCH v2 0/4] at24: move write-protect pin handling to nvmem core To: Srinivas Kandagatla Cc: Bartosz Golaszewski , Khouloud Touil , Rob Herring , Mark Rutland , baylibre-upstreaming@groups.io, LKML , linux-devicetree , linux-i2c , Linus Walleij Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org czw., 19 gru 2019 o 11:56 Srinivas Kandagatla napisa=C5=82(a): > >> > >> Thanks Khouloud for this patchset, > >> > >> I can take this via nvmem tree once we get an ack on dt bindings from = DT > >> maintainers. > >> > > > > Hi Srinivas, > > > > this will conflict with my at24 tree for this release - can you put > > those patches (once they're fine) into an immutable branch for me to > > merge in? > > I can ack nvmem core patch so that you can take it directly via at24 > tree if thats okay. > Sure, even better! Bart