From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752860AbeDDCDb (ORCPT ); Tue, 3 Apr 2018 22:03:31 -0400 Received: from mail-io0-f194.google.com ([209.85.223.194]:42078 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751332AbeDDCDa (ORCPT ); Tue, 3 Apr 2018 22:03:30 -0400 X-Google-Smtp-Source: AIpwx48lP5XZiTbjmO1rWTDEuZJcm4RwKcFBP3OH2zHJgPeyQvZ830CUYjR4eAz0IOb+f/qdtFVVphUUEurssHqZJg4= MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Tue, 3 Apr 2018 19:03:28 -0700 X-Google-Sender-Auth: cMUWYSONXpkmduPQxXX3TvDA_lo Message-ID: Subject: Re: [GIT pull] irq updates for 4.17 To: Palmer Dabbelt Cc: Thomas Gleixner , Linux Kernel Mailing List , Ingo Molnar , Arnd Bergmann Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 3, 2018 at 6:51 PM, Palmer Dabbelt wrote: > > Thanks! The linked patch set should be fully bisectable, while this one > will fail on some ARM randconfigs. If it's only some (not very realistic) randconfigs, I suspect an incremental fix is probably the easier solution, rather than redoing that whole branch. So mind at least sending that incremental fix on top of the branch to Thomas and making his life easier if he decides to go that way? And if Thomas is busy doing something else (*), and I come back to this tomorrow as-is, I'd want to pull his tree and just apply the incremental fix anyway, so it makes sense to send it to me as well. Linus (*) I have long since accepted that some people have a life outside of kernel development too, and don't always reply immediately. I may not _understand_ it, but I am resigned to the fact.