Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp880479imm; Fri, 28 Sep 2018 08:18:19 -0700 (PDT) X-Google-Smtp-Source: ACcGV61Um1Juojeadc/EioaDDeNQNdivnAUO7DYYXN3U751//ebqXhUi4cm3kYrWFZN2ANaaNgzJ X-Received: by 2002:a17:902:f209:: with SMTP id gn9mr16797735plb.173.1538147899485; Fri, 28 Sep 2018 08:18:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538147899; cv=none; d=google.com; s=arc-20160816; b=XUMqyXcm8BePBRq8sqxdpTATFm5GGUITsP44gbdgWngt8VghKAMbSdUm2qx2Cd1tqU H57V7bc/iOjDIdBFIKUXPY+pTP1kHjRApz498X0cKD2bs/8cvtX2upCWRPuevRVqOwoa jk6jgXDkBNHMsDSv1bXXXrcB8Ts5ad/1OEc0szPY5yjI0IPYfmO3ESs5GlwqBN7tzmgf vQAAmQl47Uf2nn6B4l/yCgO1mviMB2jBuvQrc8l6mwJvgxEPRqgKB3JQDRvS6JaMudRl w8hK7zw7Sp3k+Uvn/2etzWNEMip8de92x0svDRR1goP4guFxfVZjIfErvIFhHHVVzc7J Yi1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=5n1xoPPNMSxuYRMOrn1UUGIPY5EDLmggeL5YKEoFjHw=; b=shc7Nb2uWpOiSZDWHIKVZlNcVXO6KJkoezAoaMsI0m3tQzmoRuyPm4vi+t0SDikDtA +5e+dzAeSYOOe1XLAbCw4cs2+8V49KrR38ppuFfkZUWwoe/mhkSyd3VybL5gDoB3NIem aIJEmKxZncIGzPynQio+uWUSDYzHsSVcgyfy0w6q5rNlpwCFFimY31uusgWkpWmzfvh3 6JQL6kM74t0IP+Dv3ZTJKu42PsI2TWZVhj35o+CMYGqnbdmYSpuCVDekd3URTZM51bx8 Vsl0BswqXV96XWLyXwAZrbcOiBr3rab/1QRT2JPyLquvUdP66MnT64mbvEtmA3UH2inh U+0Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=2IdWCEZR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z68-v6si4881413pfz.163.2018.09.28.08.18.03; Fri, 28 Sep 2018 08:18:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=2IdWCEZR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728946AbeI1VmK (ORCPT + 99 others); Fri, 28 Sep 2018 17:42:10 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:48725 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726345AbeI1VmJ (ORCPT ); Fri, 28 Sep 2018 17:42:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=5n1xoPPNMSxuYRMOrn1UUGIPY5EDLmggeL5YKEoFjHw=; b=2IdWCEZRpI5KJst25CDxGLtta6RTAUe6QGHfrz2gTpYkE3EWuuEp41AvV/GcEMHHvptIYNJl5Wl8T0UaTC4/mNtvcNMK2R3IfyB+KM5fpSSniJlWeAhjy+pS4QnllSRbAUXGQptwTJTem720QBU5C+Ak2s8YNOtOi2Fl6hL6uT0=; Received: from andrew by vps0.lunn.ch with local (Exim 4.84_2) (envelope-from ) id 1g5uWc-0005Uh-UG; Fri, 28 Sep 2018 17:17:50 +0200 Date: Fri, 28 Sep 2018 17:17:50 +0200 From: Andrew Lunn To: "Y.b. Lu" Cc: "linux-kernel@vger.kernel.org" , "devel@driverdev.osuosl.org" , "netdev@vger.kernel.org" , Richard Cochran , "David S . Miller" , Ioana Ciocoi Radulescu , Greg Kroah-Hartman Subject: Re: [PATCH 1/2] net: dpaa2: move DPAA2 PTP driver out of staging/ Message-ID: <20180928151750.GD19396@lunn.ch> References: <20180927111228.46118-1-yangbo.lu@nxp.com> <20180927132507.GB23375@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > struct dprtc_cmd_get_irq - Putting pad at the beginning of a struct seems very > > odd. And it is not the only example. > > [Y.b. Lu] This should depended on MC firmware and APIs I think. Once the MC improves this, the APIs could be updated to fix this. That is going to be hard to do. Ideally the driver should work with any firmware version. You don't really want to force the user to upgrade the driver/kernel and the firmware at the same time. So you cannot for example remove this pad. What you might be able to do in newer versions is actually use the space. But you have to be sure the current code is correctly ignoring it and setting it to zero. Andrew