[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2tYoHSFdJzrp9MW@atomide.com>
Date: Wed, 9 Nov 2022 09:37:04 +0200
From: Tony Lindgren <tony@...mide.com>
To: Andreas Kemnade <andreas@...nade.info>
Cc: Mark Jackson <mpfj@...flow.co.uk>, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org
Subject: Re: [PATCH] Update Nanobone
Hi,
* Andreas Kemnade <andreas@...nade.info> [221108 18:38]:
> Hi,
>
> On Tue, 8 Nov 2022 17:18:54 +0000
> Mark Jackson <mpfj@...flow.co.uk> wrote:
>
> > Any update on this patch ?
> > Did it ever get through ?
>
> it got probably caught in peoples "internal spam filter"
> reasons:
> - bad subject line
> look at git log arch/arm/boot/dts/am335x-nano.dts for sane values
> - bad recipient list
> get_maintainer.pl is your friend
>
> Hmm, you already have contributed long time ago, it looks better:
> Author: Mark Jackson <mpfj-list@...flow.co.uk>
> Date: Thu Dec 15 10:52:13 2016 +0000
>
> ARM: dts: Update Nanobone dts file to add external FRAM chip
>
> That looks ok. But maybe reread the documentation/SubmittingPatches again
Hmm yeah please use similar subject line with the prefix for the dts
changes.
Looking at the dts changes only, the changes for status = "okay" changes
should not be needed for devices enabled by default. Seems like the other
changes are for rs485, please describe why the changes are made in the
patch description.
The separate defconfig should not be needed. Please send any defconfig
changes to multi_v7_defconfig or omap2plu_defconfig as separate patches.
Note that you can run make savedefconfig first to produce a minimal diff.
Then if adding device drivers, please add them as loadable modules where
possible.
Regards,
Tony
Powered by blists - more mailing lists