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=-0.3 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 3C46FC28CBC for ; Sun, 3 May 2020 20:21:18 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E159B206F1 for ; Sun, 3 May 2020 20:21:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="fSGLMr4+" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E159B206F1 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernelnewbies-bounces@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.92.3) (envelope-from ) id 1jVL6W-000540-KB; Sun, 03 May 2020 16:20:48 -0400 Received: from mail-wr1-x444.google.com ([2a00:1450:4864:20::444]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1jVL6U-00053s-C2 for kernelnewbies@kernelnewbies.org; Sun, 03 May 2020 16:20:46 -0400 Received: by mail-wr1-x444.google.com with SMTP id i10so18429086wrv.10 for ; Sun, 03 May 2020 13:20:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=s2S5KLI8fVaGapMroquMfv2l0/srUDQXDG1MDairmSw=; b=fSGLMr4+yvV/yDulyubac/haNFErBd1nNtIS0CK/YVZDq9D+sctnjwsZnPTBqbzyud L5i607gOULrIMG6NEt8UD9fKdwCkPgEHxYvwl1lOv1TezGAtZuL5LmgpwUgS89oh6Nen Xay/6KdnNCGi0hwfF/qZ20iNHxJbCPwu8hhz6ytudRAUXdaSq/Dy7+VS/oj7fdywr94a SLcqcwQ0PTKz+mKJGwYeV5QH4L6GPm0aiFJWwsNJM3L0Cf7ueVnMg+6Vp0OROvXcWugD Y9qmI8R5nQJOCB1L0hm6eNsaisDXGMtu19dJFuCDzg8zAHxVgB3vTdOZMsQMOf9cTRnf KIyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition; bh=s2S5KLI8fVaGapMroquMfv2l0/srUDQXDG1MDairmSw=; b=LPVuydIMa+h3g2QN3vRskMmi1gG5xfxkuA5qWZCEwUN5SOhcA0MPH5D8mB2S+7e1s6 g7ErTs09gXK7vlfEcugf+AlxNmSf3kFEYIHt3pWj8Wy/4oDGwpSArrHZo0pRTwy0PPy7 J4jFJLwzSCqioe3gK8AvKXTbFx9yECBeEHxuuEibZeOu1lFwMHsgpMDkXE5ZCSSgChPh qCBqibilF+AyjS6Ef3uUhtbxnN9FNeG1R+QQCyOhjFZQ3lCLm2ut+I5+5eokyd4Icytp WcYiOQkAyPUQCJTYV0EwPXMpZ5k/X6NgLQ+kqjiF9XC19kZNqsWFNcZDb9r7oBS7sK47 lFAA== X-Gm-Message-State: AGi0PuYsFzWuFAYO7/8e6r3dDEXWl9Xlh5Y0+nrhvBNHOJFxckoVmD3t PlUsPs2LYQVZrkY2B9BEeAu56KHB X-Google-Smtp-Source: APiQypJG0Oo7T7XJj0OLyWAlzLp4zDY8PCGIc60nXPe2TJdEIXtOVmV44+k2mcYOfkWbK2DWZCUjXg== X-Received: by 2002:a5d:4447:: with SMTP id x7mr15192104wrr.299.1588537182210; Sun, 03 May 2020 13:19:42 -0700 (PDT) Received: from vasteMachine (s559503e2.adsl.online.nl. [85.149.3.226]) by smtp.gmail.com with ESMTPSA id e17sm12410855wrr.32.2020.05.03.13.19.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 03 May 2020 13:19:41 -0700 (PDT) Date: Sun, 3 May 2020 22:19:35 +0200 From: Jacko Dirks To: kernelnewbies@kernelnewbies.org Subject: Getting started on writing a driver for the rpi4 Message-ID: <20200503201935.GA4193@vasteMachine> MIME-Version: 1.0 Content-Disposition: inline X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org Hello all, I want to get started on writing a driver for the I2C slave for the Raspberry Pi 4. Now, I have a feeling that I cannot just write the thing and then dump it on everyone involved, not in the last place because I have never submitted a kernel patch before. So, should I email a mailing list warning everyone of what I want to do? Is there anything else I should know about? To clarify, this is not about the creation of the driver itself, more of a meta question of how to announce that I want to do this. Thanks in advance, Jacko Dirks _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies