From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Subject: iio: rebased the togreg tree.
Date: Thu, 3 Nov 2022 21:46:25 +0000 [thread overview]
Message-ID: <20221103214625.2ae85190@jic23-huawei> (raw)
Hi All,
I hadn't been paying close enough attention to dependencies that were building
up between changes in the fixes-togreg branch / upstream and a few
patches I was carrying on the togreg tree (specifically around ms5611 and bma400
and the regulator and devm changes).
As such I decided to rebase to drop some of the problem patches for now.
Given the pain such a rebase will cause anyone using the togreg tree is pretty
much the same, whatever I rebase it on, I've moved the whole thing forward to
v6.1-rc3 on basis that includes fixes that are dependencies of some other
patches on this list and will make merging them easier.
I normally try to avoid a rebase that isn't a fast forward of the tree,
but meh, sometimes it's not worth the pain.
Jonathan
reply other threads:[~2022-11-03 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221103214625.2ae85190@jic23-huawei \
--to=jic23@kernel.org \
--cc=linux-iio@vger.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