From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lilium.sigma-star.at ([109.75.188.150]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1fAhlA-0002g2-GQ for linux-um@lists.infradead.org; Mon, 23 Apr 2018 20:08:26 +0000 Received: from localhost (localhost [127.0.0.1]) by lilium.sigma-star.at (Postfix) with ESMTP id 5FFEE18186368 for ; Mon, 23 Apr 2018 22:08:10 +0200 (CEST) From: Richard Weinberger Subject: Patchwork usage Date: Mon, 23 Apr 2018 22:08:08 +0200 Message-ID: <1708117.Q62ykoCA5g@blindfold> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-um" Errors-To: linux-um-bounces+geert=linux-m68k.org@lists.infradead.org To: linux-um@lists.infradead.org Hi! To keep track of UML related patches I'm using patchwork now. Using the following link[0] you can observe the state of patches. If a patch is marked as "accepted" I've pushed it into one of my local queues and will show up in -next soon. I push my local queues to kernel.org after I found time to did basic testing and a few patches summed up. Please note that material for the next merge window might show up in linux-next only 1-2 weeks before the merge window opens. As always, if I forget a patch feel free to shout at me. Thanks, //richard [0] https://patchwork.ozlabs.org/project/linux-um/list/?series=&submitter=&state=*&q=&archive=&delegate= -- sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria ATU66964118 - FN 374287y _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um