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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no 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 3C5DEC433DF for ; Mon, 22 Jun 2020 08:04:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0CB2C208E4 for ; Mon, 22 Jun 2020 08:04:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="V/gsFIEJ"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="tfWT9q3l" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725802AbgFVIEb (ORCPT ); Mon, 22 Jun 2020 04:04:31 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:44123 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725788AbgFVIEb (ORCPT ); Mon, 22 Jun 2020 04:04:31 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F07945C1FEB; Mon, 22 Jun 2020 04:04:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 22 Jun 2020 04:04:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=nwU8wNCod4IaT7IMdx+xqFHmuXI khyVcTMIfSTPRVBg=; b=V/gsFIEJXKnoCewOMVgd8DFwKPjkH8d0TvST3GDb/Xh 1elOgMiTmrE3p3ISUE48QEWwoofNFR5lln4MafG9s7lKxQ6zSi/jti287kzYMag+ XY+rqzHsb3fcygjSlpEfmzkU1tbeSGc0kkfk/o/NIgcB3iluPx9cVHqBOzsjq/f5 WNp6XlsH6DH3LSZrpuHYsQz0Blbv9xYYZ4Kn2sZg9q4eSTkwhSWM8ts5YXB1T4vL LsDkULZ09lrGPgDp78Bt9BagsDArEINbNMenvfnIx5negNUovN7NRECRD9qQy4+6 DYkmR0hpj4DWaSlRpQFitTgKVFxhYvNzOGcvaXhbMIQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=nwU8wN Cod4IaT7IMdx+xqFHmuXIkhyVcTMIfSTPRVBg=; b=tfWT9q3lBZAc4ImRpHXt9d cWRzKVVUq5rdReAxA2+v0NuaXvPF2e/TkSwksjUFRkalQOPKDR6zxQqrAOd/Lv94 89iEUGenOAZwxb92eDoZjw6d10b500s0odV5eyqraOC06QOU1lQ8xCuyJuTpE5Kd bTL5hYinzRBCs+e7X8BHnw7RnIRR8MKtOkQ3p8RQyIvL9TbfH0ghq6KPIBOdBzrC FuhFv38sZ1NnvLTHPgSOB6dv08xBJHaD0qGxwpCapYTHEKBohkrgGX+6osJACujY PyH7Lfc2kq+3iuttoJjcpebUUN5S9RD0N13G4yebXWe0cFzTfGjVD853jdPPNYiw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudekvdcutefuodetggdotefrodftvfcurf hrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertddttd dvnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucgg tffrrghtthgvrhhnpeeuleeltdehkeeltefhleduuddvhfffuedvffduveegheekgeeiff evheegfeetgfenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecukfhppeekfedrkeei rdekledruddtjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 7DC7B3280059; Mon, 22 Jun 2020 04:04:29 -0400 (EDT) Date: Mon, 22 Jun 2020 10:04:25 +0200 From: Greg KH To: bugzilla-daemon@bugzilla.kernel.org Cc: linux-usb@vger.kernel.org Subject: Re: [Bug 208267] usbip broken with latest kernels? Message-ID: <20200622080425.GA3363284@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Sun, Jun 21, 2020 at 05:03:25PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208267 > > --- Comment #3 from DocMAX (forum@docmax.my.to) --- > yes 5.6 works. as i said, starts with 5.7. > i haven't much experience with git bisect. need some guidance. the man page for git bisect should have lots of guidance, see man git bisect for the details. To start, do: git bisect start git bisect good v5.6 git bisect bad v5.7 and then follow the prompts from there, building and booting the resulting kernel and saying 'good' or 'bad' depending on what happened. If you have specific questions about this, please let us know.