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;
Date:   Tue, 10 Apr 2018 10:39:06 +0300
From:   Heikki Krogerus <heikki.krogerus@linux.intel.com>
To:     Tobias Regnery <tobias.regnery@gmail.com>
Cc:     gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: fix tracepoint related build error
Message-ID: <20180410073906.GC10141@kuha.fi.intel.com>
References: <20180409075517.15362-1-tobias.regnery@gmail.com>
 <20180409100153.GA10141@kuha.fi.intel.com>
 <20180409114053.GA9417@builder>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180409114053.GA9417@builder>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Tobias,

On Mon, Apr 09, 2018 at 01:40:53PM +0200, Tobias Regnery wrote:
> You are right, building a defconfig, enable the UCSI driver and disable
> CONFIG_FTRACE indeed builds without problems. So it must be some other
> combination of config options. Attached is the randconfig which triggers
> the problem with linux-next from today.
> 
> Regardless of the root cause, building trace.c conditionally on
> CONFIG_TRACING works and the build failure goes away. Grepping through
> the tree this seems to be the right option to depend on, as other users
> of tracepoints are doing the same.

Fair enough. I'll send a fix for that.


Thanks,

-- 
heikki