From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 70F6FA00C2; Mon, 26 Sep 2022 10:05:34 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 10929400D7; Mon, 26 Sep 2022 10:05:34 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 1FC58400D5 for ; Mon, 26 Sep 2022 10:05:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664179531; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=w7j1wPrMMHyaPiVCINzAVx0+BERIElhVl+qqpMnxeyA=; b=h5UnDeft/MEELO9ug6Z+H5JrjrayUDcQ8vIya92vBoBtYlRzGWMagZ2Q+7G8yRXHuKrccB 7UHuMrR8s7P35OOf3SWbujwvpKJ2GgP1yERFXjdp5EUfhR7Kvuheaqi0ELmWEnLM8jMETV kk9uFODXN1glyzKObRurqGWmVeesEPM= Received: from mail-ej1-f70.google.com (mail-ej1-f70.google.com [209.85.218.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-171-DVZl8iqlOwaPcSRpyvFoRw-1; Mon, 26 Sep 2022 04:05:30 -0400 X-MC-Unique: DVZl8iqlOwaPcSRpyvFoRw-1 Received: by mail-ej1-f70.google.com with SMTP id oz10-20020a1709077d8a00b00783c1ad301fso327769ejc.2 for ; Mon, 26 Sep 2022 01:05:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=w7j1wPrMMHyaPiVCINzAVx0+BERIElhVl+qqpMnxeyA=; b=iQJdd9DxJdi5UMLT5e3NbykgiC3IscdEzkqIH7vouaklNo/0CTJrIsReld1L2nAmap 9S3jll1g1QXmQ2ucfSvvPB+VcJ53McJJ8/PftZP7ZMYkGKGh41tcM9pZ1/TTW34bXXyX nkj15z2RG0pasdWlPZj1cp/22MfOlt3A+Cqo0xafVdeq5M4bKFpwhiBnXu6wnSpbWSqp G3aQ1FGxxKUYkkatacm5U4GiK6WoKbkT011ZXI8VlnjuXSjhibKlTbgsC/D8pFM6AZwt GYIHX3kNjkcmHPd4EH1p/hcbLacw261E/yDqBkDhfcJzhFf/BwZSUHkyay2hmvTDm4HT 3UeA== X-Gm-Message-State: ACrzQf2pmGpDUEpWrZ3KZrbGcOUkBnFzNlnF1qZYcXwgAdWwM3jMG3SS aY4IOLFncXDyQSKdGNCmtAmntOq5sj/oGVnjqCcTwcWlVEtnNd/K6iVAPvUPivHYBDKRbrwDI1R c4Rp2ziptP6kRTKkRlQk= X-Received: by 2002:a05:6402:1c0e:b0:457:4f32:fcd5 with SMTP id ck14-20020a0564021c0e00b004574f32fcd5mr3010877edb.75.1664179529370; Mon, 26 Sep 2022 01:05:29 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4+2veMD8ugS2B3U5RvToxRSvzUJAY1F7HeoRw96qrvGEqDmg1a9S4teaoiwGIWxqD0dWn4CyKKeEwi8QVBnVs= X-Received: by 2002:a05:6402:1c0e:b0:457:4f32:fcd5 with SMTP id ck14-20020a0564021c0e00b004574f32fcd5mr3010863edb.75.1664179529166; Mon, 26 Sep 2022 01:05:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Mon, 26 Sep 2022 10:05:16 +0200 Message-ID: Subject: Re: facing _apply patch failure_ warning To: "Naga Harish K, S V" Cc: "aconole@redhat.com" , "ahassick@iol.unh.edu" , "Jayatheerthan, Jay" , Jerin Jacob , "dev@dpdk.org" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Mon, Sep 26, 2022 at 9:54 AM Naga Harish K, S V wrote: > I am facing _apply patch failure_ warning for one of my patchsets as be= low. > > https://lab.dpdk.org/results/dashboard/patchsets/23622/ > > http://mails.dpdk.org/archives/test-report/2022-September/309233.html > > Looks like the patch is being applied for dpdk branch, but the patchset i= s for =E2=80=9Cdpdk-next-eventdev=E2=80=9D branch. Testing locally, the script seems to correctly identify the branch: $ ./tools/pw_maintainers_cli.py --pw-server https://patchwork.dpdk.org/api/1.2 --pw-project dpdk --pw-token XXX list-trees --type series 24817 dpdk-next-eventdev Not sure what went wrong. > > Can you help in applying the patch to correct branch (dpdk-next-eventdev)= ? I manually triggered a test of this patch against this branch. --=20 David Marchand