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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4F437C433F5 for ; Mon, 21 Feb 2022 18:41:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231847AbiBUSmS (ORCPT ); Mon, 21 Feb 2022 13:42:18 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:57072 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232321AbiBUSlw (ORCPT ); Mon, 21 Feb 2022 13:41:52 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1103062CF; Mon, 21 Feb 2022 10:40:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645468855; x=1677004855; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=uQrV/nhZGmqBQaK5yJ+b1uhayz6zJFbAKucjtUG4ATU=; b=Ssci7z2FR5RGOqHXuDCSvpUsPn2hKa6QirU8cY3kJmGUZ7rxicJ1v7H7 BKLcPC1U8sV9XwNe+NpStA8EPDXyfYk8CWPt7vrnIpCzTr1Y3u1qlXe2r LtYF/HoRAlbI/HlzlajK2T20eNIkLAS3XS28Aq/0BNBWfzphyWeheSc49 aEdqlyjO7caf/WHSggnzYTphEhtwRM0omV8Gk9UhHthxzYaqjfkpY30uX FmA0Ec5NRmz4caCqN3u+LiPSYEj1LHEbfaree+8oHFdx0LGuA8RZQNpgO IlSTEYBFO8pqgtrQIrPmcwMMWKkHDk9kq9wxti+L+pERuXpoje9ptZ0aU A==; X-IronPort-AV: E=McAfee;i="6200,9189,10265"; a="251739157" X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="251739157" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 10:40:54 -0800 X-IronPort-AV: E=Sophos;i="5.88,386,1635231600"; d="scan'208";a="490519800" Received: from smile.fi.intel.com ([10.237.72.59]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Feb 2022 10:40:53 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nMDbN-006siK-Ra; Mon, 21 Feb 2022 20:40:01 +0200 Date: Mon, 21 Feb 2022 20:40:01 +0200 From: Andy Shevchenko To: Johan Hovold Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, Wolfram Sang , syzbot+0591ccf54ee05344e4eb@syzkaller.appspotmail.com Subject: Re: [PATCH v1 1/1] i2c: robotfuzz-osif: Propagate parent device to I2C core Message-ID: References: <20220204151726.8924-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 21, 2022 at 10:56:20AM +0100, Johan Hovold wrote: > On Fri, Feb 04, 2022 at 05:17:26PM +0200, Andy Shevchenko wrote: > > I2C core might use parent device to retrieve properties of > > the controller. Propagate parent device for that. > > What is the problem you're trying to solve here? Okay, let's drop the patch. -- With Best Regards, Andy Shevchenko