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 DDD78C19F2D for ; Tue, 9 Aug 2022 22:22:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230027AbiHIWWt (ORCPT ); Tue, 9 Aug 2022 18:22:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45224 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229569AbiHIWWt (ORCPT ); Tue, 9 Aug 2022 18:22:49 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 1A3355D0C1 for ; Tue, 9 Aug 2022 15:22:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1660083765; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=J5d/3BG2s8vMnjAuoCduflI1NT5l+CFjuPlkuPIekQ4=; b=ZBTqCZhzK/VGqa3plYSRvgkuNKDpgqx55hQ8xP1HWWZagoPkuJjpGvcZFgjAV7EYHgjioN 1xs/1DrZ9XQ18sHwjnKSSBW5zkrfLptSEAkcOKMRqF56LvkehpjC9Gdp5AV7Dxdbj8jAl/ EKK6EAukwbfmO+eDmGdOPYj7LC+YGaY= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-524-OCdqLyg2NhStXh5SSmRGWg-1; Tue, 09 Aug 2022 18:22:43 -0400 X-MC-Unique: OCdqLyg2NhStXh5SSmRGWg-1 Received: by mail-wm1-f70.google.com with SMTP id b4-20020a05600c4e0400b003a5a96f1756so176794wmq.0 for ; Tue, 09 Aug 2022 15:22:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=J5d/3BG2s8vMnjAuoCduflI1NT5l+CFjuPlkuPIekQ4=; b=kj7P6znLmKspBObkX5MzUCX46f91P6lszZNNUelQUY0SYaoqC8Nfy7ONX6vUiAr/Um bv5AFlN1C+x0uLZWBe8SNnh7tg2Q5JlnOGFTPXmX2kEZhPrI/Usr45SOGa1ixk6vBBts NmVaEqeKDevyUvWtM9XmIED9iGP0O8naCqENzW3Z6EnEN59200x0HnIl7xuYfOMYY8c6 nzCrRk+9Ffx+JpbrBx7eaMpaKt9Ee3dbHd167+evAME6QB81TZK5y9uwVbXo/T01L+H/ bLK1UCAs+ohF1muu2QMgcH8gdOLbMYbjfHgGzgTGDx1708ZQAylp+h/RIKm0G8/cQto7 51AA== X-Gm-Message-State: ACgBeo0a/iDcTPpWbFCDL+IGzoZ1nkdehuxmMr1WIYnKBr81WxYsXyW/ 93LC+G2BYUuN/ta/KyoUOOeTtGX2fvcBczj5uYV6Nli1m8RlhkZwuQpZ2esoNNMz/yZPcAc8gAJ RpvBmlK4gl4yx1E9awcoOVQ== X-Received: by 2002:a7b:c2a9:0:b0:3a4:f2a8:e7e4 with SMTP id c9-20020a7bc2a9000000b003a4f2a8e7e4mr302182wmk.55.1660083762775; Tue, 09 Aug 2022 15:22:42 -0700 (PDT) X-Google-Smtp-Source: AA6agR4kBbpAEN6yiWnogwaGnmyCFzjP3Rldih06PHvfx/pIR7xi/W68poKipCx4qbM6a5cpTN/uuQ== X-Received: by 2002:a7b:c2a9:0:b0:3a4:f2a8:e7e4 with SMTP id c9-20020a7bc2a9000000b003a4f2a8e7e4mr302175wmk.55.1660083762522; Tue, 09 Aug 2022 15:22:42 -0700 (PDT) Received: from redhat.com ([2.52.152.113]) by smtp.gmail.com with ESMTPSA id 5-20020a05600c028500b003a3278d5cafsm242111wmk.28.2022.08.09.15.22.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 09 Aug 2022 15:22:41 -0700 (PDT) Date: Tue, 9 Aug 2022 18:22:38 -0400 From: "Michael S. Tsirkin" To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: Signed-off-bys missing for commits in the vhost tree Message-ID: <20220809181520-mutt-send-email-mst@kernel.org> References: <20220810080139.71f67609@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220810080139.71f67609@canb.auug.org.au> Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Wed, Aug 10, 2022 at 08:01:39AM +1000, Stephen Rothwell wrote: > Hi all, > > Commits > > 2d84b3963557 ("ack! tools/virtio: drop phys_addr_t typedef") > c6d14c52fba9 ("ack! tools/virtio: drop phys_addr_t typedef") > > are missing Signed-off-bys from their author and committer. > > Is this new set of commits really ready and destined for the current > merge window? Oh sorry. They are empty, they just record that I need to add an ack to the log of the previous commit. So harmless - I just forgot to squash them - I would normally notice as I prepare the pull request. Fixed - if you can pick up the new hash I just pushed pls do but if not it's okay to test as is, too. -- MST