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=-15.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PULL_REQUEST, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=ham 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 0C070C7618B for ; Wed, 24 Jul 2019 15:41:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D6121217F4 for ; Wed, 24 Jul 2019 15:41:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563982906; bh=rqy4inXJX4EStiJqMCkbOxZevjFiaHCLGF8JG3FIjXg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=2tWvIWxe4+qfw0Oe6mct2qYnHCX7Gd07sRQZxtsguEMiDKAzlmQOGwsM4XeIXZozK +RzGqreAxhBj2Rjf6y3z7EKR+LvYwgeDPUf4I9A0IvhGuIuVLjYNgwDOme9bzsEuR4 cnHey5hQ1GOeT4MM5m0qBaVgsbWpmc/eY87P9T68= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728116AbfGXPlp (ORCPT ); Wed, 24 Jul 2019 11:41:45 -0400 Received: from mail.kernel.org ([198.145.29.99]:46756 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726958AbfGXPlp (ORCPT ); Wed, 24 Jul 2019 11:41:45 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8025F217F4; Wed, 24 Jul 2019 15:41:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563982904; bh=rqy4inXJX4EStiJqMCkbOxZevjFiaHCLGF8JG3FIjXg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=04SEi1WZ7Su1Ya4b2dDRG5xUM7J3cw3ngsNjHx3hvSlPmRVIMUbgDc2jv/EWnDBVf HzYw19+alfLSSwVNi5dxFxprFjEaPAALIkhggpEIaPOada67HMXQrDVBXtG6CAY74Z 8KXBoamfZ2pxP8VyjrgTI7+b1Y91EjbmfaaQDT98= Date: Wed, 24 Jul 2019 17:41:41 +0200 From: Greg KH To: Moritz Fischer Cc: linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org, broonie@kernel.org Subject: Re: [GIT PULL] FPGA Manager fix for 5.3 Message-ID: <20190724154141.GA3171@kroah.com> References: <20190724052012.GA3140@archbox> <20190724072056.GA27472@kroah.com> <20190724145513.GA24455@archbox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190724145513.GA24455@archbox> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 24, 2019 at 07:55:13AM -0700, Moritz Fischer wrote: > On Wed, Jul 24, 2019 at 09:20:56AM +0200, Greg KH wrote: > > On Tue, Jul 23, 2019 at 10:20:12PM -0700, Moritz Fischer wrote: > > > The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b: > > > > > > Linus 5.3-rc1 (2019-07-21 14:05:38 -0700) > > > > > > are available in the Git repository at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git tags/fixes-for-5.3 > > > > > > for you to fetch changes up to c3aefa0b8f54e8c7967191e546a11019bc060fe6: > > > > > > fpga-manager: altera-ps-spi: Fix build error (2019-07-23 17:29:17 -0700) > > > > > > ---------------------------------------------------------------- > > > FPGA Manager fixes for 5.3 > > > > > > Hi Greg, > > > > > > this is only one (late) bugfix for 5.3 that fixes a build error, > > > when altera-ps-spi is built as builtin while a dependency is built as a > > > module. > > > > > > This has been on the list for a while and I've reviewed it. > > > > > > Signed-off-by: Moritz Fischer > > > > This message is not in the signed tag in the repo, are you sure you make > > this correctly? All I see is the first line: > > FPGA Manager fixes for 5.3 > > > > And it's a singluar "fix" :) > > Yeah, over the top. I wanted to figure out the workflow with an easy > example ... and ... learned something again :) > > So basically the message above is what is supposed to go into the tag > message? Yes, and then git pull-request takes that and puts it into the message to send me. thanks, greg k-h