All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Malysa <greg.malysa@timesys.com>
To: u-boot@lists.denx.de
Cc: Ian Roberts <ian.roberts@timesys.com>,
	 Nathan Barrett-Morrison <nathan.morrison@timesys.com>
Subject: Upcoming Analog Devices SoC Support Submission
Date: Mon, 25 Mar 2024 22:47:30 -0400	[thread overview]
Message-ID: <CAAjXUar=97omadi8MSLox5V_iCwix+YSUP_fMCGsLhUzUfBpcw@mail.gmail.com> (raw)

Hi Tom,

I wanted to get a little bit of guidance before dumping some patches
on the mailing list. I've been preparing to submit support we've
developed for the Analog Devices SC5xx SoCs including both core SoC
support and specific device trees and defconfigs for the eval kits
available from ADI. I've submitted several small patches to touch
various shared parts of U-Boot that we needed to extend to get this
hardware running and to get some familiarity with using patman to
format and submit things, but now I have a roughly 15k line changeset
consisting of a new mach type and all of the required drivers for the
system. It's broken down into a bunch of commits: one for the mach
type support, one per driver we've added, and one per target board
supported.

What is the best way to submit this? Ideally I'd love to get feedback
on individual drivers from the respective subsystem maintainers, but
it seems rude to have a 20-element patch series that gets resubmitted
each time feedback comes in for one component. If we break it down
into separate patches for each piece, what would be the best way to
ensure that all of the dependencies are merged in order?

Thanks,
Greg

-- 
Greg Malysa
Timesys Corporation

             reply	other threads:[~2024-03-26  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  2:47 Greg Malysa [this message]
2024-03-28 20:47 ` Upcoming Analog Devices SoC Support Submission Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAjXUar=97omadi8MSLox5V_iCwix+YSUP_fMCGsLhUzUfBpcw@mail.gmail.com' \
    --to=greg.malysa@timesys.com \
    --cc=ian.roberts@timesys.com \
    --cc=nathan.morrison@timesys.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.