From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Jim Quinlan <jim2101024@gmail.com>,
james.quinlan@broadcom.com, linux-pci@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH] fixup! PCI: brcmstb: Add control of subdevice voltage regulators
Date: Wed, 12 Jan 2022 15:55:19 -0600 [thread overview]
Message-ID: <20220112215519.GA287022@bhelgaas> (raw)
In-Reply-To: <20220112215000.GA4972@wunner.de>
On Wed, Jan 12, 2022 at 10:50:00PM +0100, Lukas Wunner wrote:
> On Wed, Jan 12, 2022 at 06:00:11PM +0000, Lorenzo Pieralisi wrote:
> > On Wed, Jan 12, 2022 at 11:51:06AM -0600, Bjorn Helgaas wrote:
> > > On Tue, Jan 11, 2022 at 08:31:00PM -0500, Jim Quinlan wrote:
> > > What's this connected to? Is this a fix for a patch that has already
> > > been merged? If so, which one? If it's a standalone thing, it needs
> > > a commit log and a Signed-off-by. Actually, that would be good in any
> > > case. Maybe a lore link to the relevant patch?
> >
> > I was about to reply. It is a fixup for one of the branches I am
> > queueing for v5.17 (pci/brcmstb), I can either squash that it myself or
> > you can do it, provided that Jim gives us the commit id this is actually
> > fixing (or a lore link to the patch posting so that we can infer the
> > commit to fix).
>
> If you apply the patch to the pci/host/brcmstb branch with "git am"
> as usual, then execute "git rebase --autosquash v5.16-rc1",
> git will automatically figure out the commit id this patch is fixing,
> fold it into the commit and rebase the remainder of the branch on top
> of it.
Wow! That's ... amazing. Or something :)
I already did it the old-fashioned way, but I'll try to remember this
trick for next time.
next prev parent reply other threads:[~2022-01-12 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 1:31 [PATCH] fixup! PCI: brcmstb: Add control of subdevice voltage regulators Jim Quinlan
2022-01-12 17:51 ` Bjorn Helgaas
2022-01-12 18:00 ` Lorenzo Pieralisi
2022-01-12 18:57 ` Jim Quinlan
2022-01-12 21:50 ` Lukas Wunner
2022-01-12 21:55 ` Bjorn Helgaas [this message]
2022-01-12 19:47 ` Bjorn Helgaas
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=20220112215519.GA287022@bhelgaas \
--to=helgaas@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukas@wunner.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 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 NNTP newsgroup(s).