Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752181AbdI2NO6 (ORCPT ); Fri, 29 Sep 2017 09:14:58 -0400 Received: from mr11p00im-asmtp003.me.com ([17.110.69.254]:59344 "EHLO mr11p00im-asmtp003.me.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751349AbdI2NO5 (ORCPT ); Fri, 29 Sep 2017 09:14:57 -0400 X-Greylist: delayed 575 seconds by postgrey-1.27 at vger.kernel.org; Fri, 29 Sep 2017 09:14:57 EDT MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-09-29_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709290189 Message-id: <1506690885.1771.6.camel@icloud.com> Subject: Re: How to verify linux-next From: Damian Tometzki To: valdis.kletnieks@vt.edu, Pintu Kumar Cc: linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org Date: Fri, 29 Sep 2017 15:14:45 +0200 In-reply-to: <159555.1506688878@turing-police.cc.vt.edu> References: <159555.1506688878@turing-police.cc.vt.edu> X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 807 Lines: 30 Hello, Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 Host: Windows 10 Guest: Ubuntu 16.04 Best regards Damian Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletnieks@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I have a general question. > > How do we normally verify linux-next tree? > The same exact way you "verify" any other Linux kernel, for whatever > definition of "verify" you plan to use. > > > > > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next > > kernel is not booting. > Does an Ubuntu kernel boot correctly under VirtualBox?  If not, fix > that issue first.  Also, "is not booting" isn't detailed enough for > anybody > to make even a guess as to what's wrong. > > Also, note that 5.1.28 is out.