From: Conor Dooley <conor@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Conor.Dooley" <conor.dooley@microchip.com>,
soc@kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V Devicetrees for v6.10
Date: Wed, 8 May 2024 21:19:54 +0100 [thread overview]
Message-ID: <20240508-unpaved-courier-fefe1f81897d@spud> (raw)
In-Reply-To: <9031c5c8-1e93-491d-b756-5794cb87d1cb@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
On Tue, May 07, 2024 at 02:15:39PM +0200, Arnd Bergmann wrote:
> On Tue, May 7, 2024, at 12:21, Conor Dooley wrote:
> > Cool, just wasn't sure if you were intentionally contradicting yourself
> > or if the "below" part had just been some general remarks. I'll try to
> > get a "revised" PR sent tomorrow.
>
> Ok. To clarify: basing on a bugfix pull request is always fine
> since those are already in Linus' tree by the time I send my
> pull requests to him for the merge window, so the branch contents
> as seen by 'git request-pull' are clean.
Ye, I was pretty sure that this is what you meant, but didn't wanna have
my second attempt also go awry!
>
> I also try hard (in general) to avoid dependencies between the
> soc/dt branch and any of the other branches, to be sure that
> there are no incompatible binding changes. This wasn't a
> problem here (I think), but if you send something late in the
> cycle, I pretty much don't want to have to think about that.
If there's anyone you don't need to worry about making incompatible
binding changes like that, it's probably Krzysztof or I. It'd be a
bit hypocritical of me to send you stuff like that..
I sent an "take 2" PR there, once the rebased branch had a chance to
appear in linux-next.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-05-08 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 15:24 [GIT PULL] RISC-V Devicetrees for v6.10 Conor Dooley
2024-05-07 9:27 ` Arnd Bergmann
2024-05-07 9:58 ` Conor Dooley
2024-05-07 10:08 ` Arnd Bergmann
2024-05-07 10:21 ` Conor Dooley
2024-05-07 12:15 ` Arnd Bergmann
2024-05-08 20:19 ` Conor Dooley [this message]
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=20240508-unpaved-courier-fefe1f81897d@spud \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=linux-riscv@lists.infradead.org \
--cc=soc@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).