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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 06443C433F5 for ; Mon, 3 Jan 2022 16:35:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233875AbiACQfE (ORCPT ); Mon, 3 Jan 2022 11:35:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40520 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233994AbiACQfE (ORCPT ); Mon, 3 Jan 2022 11:35:04 -0500 Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0BC93C061761 for ; Mon, 3 Jan 2022 08:35:04 -0800 (PST) Received: by mail-wr1-x42e.google.com with SMTP id e5so70919484wrc.5 for ; Mon, 03 Jan 2022 08:35:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=T3i9zgwcayeVl7cWKMRosEJ4OOhKmrBVCf1DuyQd0ZQ=; b=RCUaoyJ8tstUuLAgGQdCMqjsBhS4AyDd1/vb1OGi7sZXmNZg0AVF09KzJY55SMrOC8 BmAsBLhu+de4Kk0F4X/aSuyK16euq/BSzIHaZC69KVLlv7to4DJc5XFMyp0SBgNkmM8S tOAGUGP1WeSR+HiF4cZSYlzjCtE5W1UQBHzIxKU+KgWco/ik9v25waLqEiJ+SixDe0Zh HUwAqUEhJltFYvSk35b7WFJFpWMAO3fTBFg9n7emkb/ZLmYDBm5AC/MqAB6J5vGtmYUL Pyus9RPN1hHm3SVRlRpqlLUovM+UdhLUPq7NYvk9gN9xp/Gsakn5CDDNu9prgw1hqE9c OObA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=T3i9zgwcayeVl7cWKMRosEJ4OOhKmrBVCf1DuyQd0ZQ=; b=Mk2S9jvyhUrzw3dLnC7nByEvuKgtLeQoabF+V5bNajEObgpc1IY0ANvK3HNuB3ymee 6J+QUg8C5A+oAdfb93umXNEsgCMWHo2i4K1fCZfFuGbbHHzDWJ3/AZaY9i7pSrppEl8k QmXZLUz+T2rmiuxrs9vlJeFdTu21kiyZ34lqHsbA99Y5vlplkmw8Ky5RDITNmHEeMgIU dWL3mhEcpFOzroPjJboS7brz+HzX3zvddjzMvL35rpXn3eGt+xvY4IMrQdEIuZCOR216 H6mR1QjcMdzFlVfWxtxc7GZhLcFlj0mYCVNoGoWeK7AUtXzb4v4BBy6BiLGQ9vtzNrEt 8Umw== X-Gm-Message-State: AOAM5308EmlllFDxZ4O+RHVMOQgiDPNtfyE3A5PB3xwD5T0hE+JlUoqJ Os/5xf6/v36XXhLL1oryD0Rk5g== X-Google-Smtp-Source: ABdhPJw8ZtseazM51WUqhtiDVXvitp+YDlIfXCPd0LTC+fJ/cPh2CMZqRThBa00IrdH/HQDGzeNZOw== X-Received: by 2002:a5d:58dc:: with SMTP id o28mr38899290wrf.217.1641227702500; Mon, 03 Jan 2022 08:35:02 -0800 (PST) Received: from ?IPv6:2001:861:44c0:66c0:7c9d:a967:38e2:5220? ([2001:861:44c0:66c0:7c9d:a967:38e2:5220]) by smtp.gmail.com with ESMTPSA id l10sm20389876wmq.7.2022.01.03.08.35.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 Jan 2022 08:35:02 -0800 (PST) Subject: Re: [PATCH V3 1/6] tty: serial: meson: Drop the legacy compatible strings and clock code To: Greg Kroah-Hartman Cc: linux-serial@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org, Jiri Slaby , Vyacheslav , Kevin Hilman , Jerome Brunet , Martin Blumenstingl , Yu Tu References: <20211230102110.3861-1-yu.tu@amlogic.com> <20211230102110.3861-2-yu.tu@amlogic.com> <3865f01c-83f7-a69d-6835-c26f662629b7@baylibre.com> From: Neil Armstrong Organization: Baylibre Message-ID: <257d153c-960a-59fc-dfa9-5e160e42b68d@baylibre.com> Date: Mon, 3 Jan 2022 17:35:01 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-serial@vger.kernel.org On 03/01/2022 17:29, Greg Kroah-Hartman wrote: > On Mon, Jan 03, 2022 at 04:29:56PM +0100, Neil Armstrong wrote: >>>> Would it be possible we also receive the notification when those patches are applied ? >>>> Maybe a MAINTAINERS entry is missing so we can receive them ? >>> >>> That would be good, so that people can review the patches. Otherwise I >>> have to just guess :) >> >> exact, I naively thought it would be matched in the: >> N: meson >> entry but it seems an proper entry for drivers/tty/serial/meson_uart.c is needed. > > Try it, does that work when running get_maintainer.pl on this patch? Yes it does work, so no problem here > >>>> It would help me track those TTY and USB patches more easily. >>> >>> I recommend MAINTAINERS entries for drivers that are not listed and that >>> you care about seeing the changes for. >> >> This is why we have a regex to match these. > > Great, the submitter should have used that. > >> I can submit a patch to have a proper entry if the regex is not enough/appropriate. > > Whatever makes the tools work is fine with me. > >> BTW can you point us how are selected the recipients of the notification messages you send ? > > For when I apply a patch, everyone on the ack/signed-off-by/reviewed-by > list gets a response. I do not hit mailing lists with the notification > as that's just too much noise. > > Been doing it this way for well over a decade now, nothing new here :) Ok right, no problem, other maintainers (e.g: net, sound) and default b4 behavior is to send notification to same recipient as original patch. It it fits everyone for a decade, no need to change ! We have very low patches for tty & usb anyway Neil > > thanks, > > greg k-h >