From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
list@opendingux.net, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH 0/9] MIPS: CI20: Add WiFi / Bluetooth support
Date: Thu, 15 Jun 2023 11:08:04 +0200 [thread overview]
Message-ID: <20230615090804.GA8625@alpha.franken.de> (raw)
In-Reply-To: <E1q9iWM-0004zB-00@elvis.franken.de>
On Thu, Jun 15, 2023 at 10:39:53AM +0200, Paul Cercueil wrote:
> Thomas: are you able to drop this series from mips-next, or should I/we send fixup patches instead?
as I'm not rebasing mips-next I need fixup patches. This won't solve
bisectability, but not doing rebases is the what Linus prefers.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next parent reply other threads:[~2023-06-15 9:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1q9iWM-0004zB-00@elvis.franken.de>
2023-06-15 9:08 ` Thomas Bogendoerfer [this message]
2023-06-15 9:32 ` [PATCH 0/9] MIPS: CI20: Add WiFi / Bluetooth support H. Nikolaus Schaller
[not found] <20230615084006.79194526F801@goldelico.com>
2023-06-15 8:45 ` H. Nikolaus Schaller
2023-06-15 9:14 ` H. Nikolaus Schaller
2023-06-15 12:28 ` H. Nikolaus Schaller
2023-06-16 20:21 ` H. Nikolaus Schaller
2023-06-17 10:45 ` H. Nikolaus Schaller
2023-06-18 11:51 ` Paul Cercueil
2023-06-18 13:58 ` Paul Cercueil
2023-06-19 4:42 ` H. Nikolaus Schaller
2023-06-19 4:42 ` H. Nikolaus Schaller
2023-06-04 14:56 Paul Cercueil
2023-06-09 8:23 ` Thomas Bogendoerfer
2023-06-15 7:08 ` H. Nikolaus Schaller
2023-06-15 7:00 ` H. Nikolaus Schaller
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=20230615090804.GA8625@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=list@opendingux.net \
--cc=paul@crapouillou.net \
--cc=robh+dt@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