From: ada@thorsis.com (Alexander Dahl)
To: linux-arm-kernel@lists.infradead.org
Subject: Patch submission process about at91 DTS
Date: Thu, 01 Feb 2018 09:29:24 +0100 [thread overview]
Message-ID: <2019072.DmFbzY6CId@ada> (raw)
In-Reply-To: <20180131170453.GA16869@tp.shaiton.org>
Hello K?vin,
Am Mittwoch, 31. Januar 2018, 18:04:53 CET schrieb K?vin Raymond:
> My current patches are based an tested over the linux repo[0] against the
> master branch (4e19652 Update the RISC-V MAINTAINERS file).
>
> Should I rebase them against the linux-at91[1] repository? Which branch,
> at91-next? I would love them to reach the 4.14 branch but am not sure of
> the right path to submit those changes.
As far as I understood the process, it is common to base those patches on the
last tag of Linus' tree at the time sending. At the moment this would be
v4.15, in two weeks it will be v4.16-rc1. If you rebase it on top another
tree, add this information to your introductory mail.
Greets
Alex
next prev parent reply other threads:[~2018-02-01 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 17:04 Patch submission process about at91 DTS Kévin Raymond
2018-02-01 8:29 ` Alexander Dahl [this message]
2018-02-01 9:03 ` Florian Vaussard
2018-02-01 9:17 ` Nicolas Ferre
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=2019072.DmFbzY6CId@ada \
--to=ada@thorsis.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox