From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH] i2c: Mark instantiated device nodes with OF_POPULATE Date: Wed, 10 Jun 2015 09:18:07 -0500 Message-ID: References: <1422083789-18905-1-git-send-email-pantelis.antoniou@konsulko.com> <20150422074019.GA1511@katana> <20150506183733.GA1513@katana> <20150610054034.GB1573@katana> <20150610124949.GC1592@katana> <20150610140815.GA21540@katana> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20150610140815.GA21540@katana> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Wolfram Sang , Pantelis Antoniou Cc: Kevin Hilman , Guenter Roeck , Matt Porter , Greg Kroah-Hartman , Grant Likely , "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-i2c@vger.kernel.org On Wed, Jun 10, 2015 at 9:08 AM, Wolfram Sang wrote= : >> > IIRC it is the one which adds OF_POPULATED. If so, why is this not >> > scheduled for 4.1 as this bugfix depends on it? >> >> No idea. This is an obvious bugfix. > > Dunno if you did but mentioning after the commit message where you th= ink > it should be applied is very helpful for maintainers. +1 >> I would like to, yes. It=E2=80=99s just the nature of the process wh= en dealing with >> multiple kernel trees. I would be happy for someone to pick up and q= ueue it >> for 4.1. > > That might be too late now... You could also have sent the patch to m= e > so that I could apply it via i2c with rob's ack. Next time... That is exactly what I suggested on Jan 26 and Wolfram asked to resend with my ack. Pantelis sent it on Apr 24 (w/o my ack) and I applied it on May 29. Wolfram acked it, so I assumed you were not picking it up. It sat there for over a month, so it must not have been critical to apply for 4.1. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html