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 25A8AA0548; Thu, 2 Dec 2021 21:18:22 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A116940692; Thu, 2 Dec 2021 21:18:21 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 255D44067B for ; Thu, 2 Dec 2021 21:18:20 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1638476299; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n++zugARP7lgA4czXrIvgxylgjPvN4/Vdm7mbjGVgQ0=; b=OUgx8MaYebPJqcJMrZWXSiUMpmbVkpDlO9ViRrMMeASYepDP3afRBTYlnAq6VHqEH0O7Me yjfVE0/eh9/mGPKR898UJ35suhV9ng1FKyRr1TuYOij41xgKGzSjgK7Hqev3XmGaxBhrss vr5WNRduwvjDYvcFiFij7wp7qdppLPQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-548-RU0Hw0cFNXK1Vds6OyGVfA-1; Thu, 02 Dec 2021 15:18:14 -0500 X-MC-Unique: RU0Hw0cFNXK1Vds6OyGVfA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BC44C83DD21; Thu, 2 Dec 2021 20:18:13 +0000 (UTC) Received: from [10.39.208.32] (unknown [10.39.208.32]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4321D60843; Thu, 2 Dec 2021 20:18:03 +0000 (UTC) Message-ID: <2790f1a6-a391-4f1d-6149-d1342bf94104@redhat.com> Date: Thu, 2 Dec 2021 21:18:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 To: Christian Ehrhardt , David Marchand , "stable@dpdk.org" , Chenbo Xia , "dev@dpdk.org" References: <20211130165621.2467243-1-christian.ehrhardt@canonical.com> From: Maxime Coquelin Subject: Re: please help backporting some patches to stable release 19.11.11 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 Hi Christian, On 12/2/21 14:45, Christian Ehrhardt wrote: > On Tue, Nov 30, 2021 at 5:56 PM wrote: >> >> Hi commit authors (and maintainers), >> >> Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh >> I didn't apply following commits from DPDK main to 19.11 >> stable branch, as conflicts or build errors occur. >> >> Can authors check your patches in the following list and either: >> - Backport your patches to the 19.11 branch, or >> - Indicate that the patch should not be backported >> >> Please do either of the above by December the 14th 2021 (More time than >> usual as backports get harder). > > Sorry, but to meet some deadlines by test/verification I need to reduce the > time for backports to make it into -rc1 to the 9th of December. > > That still is 7 days out from now and still longer than usual. > > >> You can find the a temporary work-in-progress branch of the coming 19.11.11 >> release at: >> https://github.com/cpaelzer/dpdk-stable-queue >> It is recommended to backport on top of that to minimize further conflicts or >> misunderstandings. >> >> Some notes on stable backports: >> >> A backport should contain a reference to the DPDK main branch commit >> in it's commit message in the following fashion: >> [ upstream commit ] >> >> For example: >> https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb >> >> When sending the backported patch, please indicate the target branch in the >> subject line, as we have multiple branches, for example: >> [PATCH 19.11] foo/bar: fix baz >> >> With git format-patch, this can be achieved by appending the parameter: >> --subject-prefix='PATCH 19.11' >> >> Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". >> >> FYI, branch 19.11 is located at tree: >> https://git.dpdk.org/dpdk-stable >> >> Thanks. >> >> Christian Ehrhardt >> >> --- >> ... >> b72099be7f David Marchand net/virtio-user: fix init when using existing tap This commit should not be backported. We deliberately omitted adding the Fixes tag and Cc'ing stable@dpdk.org so that it is not automatically backported. Regards, Maxime