From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qk1-f170.google.com (mail-qk1-f170.google.com [209.85.222.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 11C2620FBB for ; Wed, 12 Jul 2023 19:18:25 +0000 (UTC) Received: by mail-qk1-f170.google.com with SMTP id af79cd13be357-7659cb9c42aso608982385a.3 for ; Wed, 12 Jul 2023 12:18:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1689189504; x=1691781504; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=n3NfvS1jvjSB+tBL+SX8HbtSmmr9dhlhzwK2rZUd5Hc=; b=dCs5IkXZ3NGwwWVD2+6l3HG1yX4rIm7pHDfgE6cmqIpiezjKcmgHr7dvv56eeGNyFP btslk8+4C4Te9R+XR9ez4WLZSK88YmjEs/TSOzWoLb/EW90IPmLlWsYvj889StnKY9Wt +6dr4jJcE9OAP4WgoSQGbIg50maY+fDWa72OU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689189504; x=1691781504; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=n3NfvS1jvjSB+tBL+SX8HbtSmmr9dhlhzwK2rZUd5Hc=; b=IeFmeYvYgH1+k6q274vbRJKwyAj/tL0kySTjprYZQ8FBNIrBo8vb/CQ7z/WSJzJS+l +Zo6dmgBbk152L6q7Ltcore4Zyt184Rbknvf3zqJhCEqYIwV8ozYRAPIUCduVswi698F NWY4yBPkx/BsUgVaBjbDVj+baqxC9obFrmYPIGauRi59Hho7+yRkrJ8+8IRPZ0DtSKr8 vyTESFaXmOZ8eU3c85a/iHIk9YYNPXPhefwn/RmbR3mOzgFRFs6QBknsaraEHqSrFo9M c+XOuQhXLzhgWIA19/kkX68AJW9cBrk5i1enQtC+g3PlEEsT2k9wfQIkSLjnFocvdtTN apjw== X-Gm-Message-State: ABy/qLYSEJJ9ZTiyCTtsyJZTR+zMbtHYJW8hVafBSGHNXLC4+mDTbqoo 3hHmOypQGaTuNLxo0a3UPk0MLaOCkv4vZan8eTs= X-Google-Smtp-Source: APBJJlGyDg5JL8Q3d6ucZpXkKk00x+YQsykrtb5V8+HD2MWk/fFqLoMePSOsg5z16Hr3t55IzzccRg== X-Received: by 2002:a05:620a:2b31:b0:766:ff0b:7ea6 with SMTP id do49-20020a05620a2b3100b00766ff0b7ea6mr18584528qkb.75.1689189504687; Wed, 12 Jul 2023 12:18:24 -0700 (PDT) Received: from meerkat.local ([209.226.106.132]) by smtp.gmail.com with ESMTPSA id i2-20020a05620a074200b00767d839aa86sm2362984qki.68.2023.07.12.12.18.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 12 Jul 2023 12:18:24 -0700 (PDT) Date: Wed, 12 Jul 2023 15:18:15 -0400 From: Konstantin Ryabitsev To: Mark Brown Cc: Andy Shevchenko , tools@linux.kernel.org Subject: Re: [PATCH v2 0/4] ASoC: rt5677: Refactor GPIO and use device_get_match_data() Message-ID: <20230712-smudge-overthrow-46457c@meerkat> References: <20230630172155.83754-1-andriy.shevchenko@linux.intel.com> <168916242630.46574.7633971537485557226.b4-ty@kernel.org> <20230712-semifinal-expansive-f9189b@meerkat> <9327ba4e-2df7-4eba-85c5-4da7bd64d2fa@sirena.org.uk> <20230712-overact-conjoined-74c85e@meerkat> <8a6e591d-6e07-4b9f-88e7-443bdc0508d2@sirena.org.uk> Precedence: bulk X-Mailing-List: tools@linux.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <8a6e591d-6e07-4b9f-88e7-443bdc0508d2@sirena.org.uk> On Wed, Jul 12, 2023 at 07:59:24PM +0100, Mark Brown wrote: > > But I think the complaint was about the merge commits being cut off: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=5a043fd5c74c66897ad113e5ee34e9361e3f4c11 > > Oh, I see. The commit in the mail looked like it might be off and it > was in reply to the applied mail so I thought that was what was being > referenced. > > > When I try "b4 shazam -M", the merge commit looks different to me, so I want > > to understand how the merge commit is generated in your workflow. > > That's generated by my scripts based on the .cover that b4 writes out > and some sed at the point where a merge is done. There's a bunch of CI > happens between applying the patches and me actually merging them so I > don't use b4 for that bit. It's just picking the subject line out with > sed so there's no way it's going to handle multi-line subjects. Will it help if b4 optionally writes out a foo.merge file in addition to foo.cover in the same format as with "b4 shazam"? -K