mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V devicetrees fixes for v7.3-rc
Date: Mon, 12 Oct 2026 09:58:09 +0100	[thread overview]
Message-ID: <20261012-ridden-paralysis-c095f7e937d7@spud> (raw)
In-Reply-To: <ab03d380-f49d-4eaf-9e8a-e8b09d1d0195@app.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]

On Mon, Oct 12, 2026 at 10:10:25AM +0200, Arnd Bergmann wrote:
> On Fri, Sep 25, 2026, at 18:56, Conor Dooley wrote:
> >
> > are available in the Git repository at:
> >
> >   git@gitolite.kernel.org:pub/scm/linux/kernel/git/conor/linux 
> > tags/riscv-dt-fixes-for-v7.3-rc
> >
> 
> Hi Conor,
> 
> I replaced this with the corresponding https://git.kernel.org/ URL
> in order to pull it, otherwise I get
> 
> $ b4 pr 20260925-parlor-snowfield-6ca46312a610@spud
> Looking up 20260925-parlor-snowfield-6ca46312a610@spud
> Looking at: [GIT PULL] RISC-V devicetrees fixes for v7.3-rc
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/conor/linux uses unsupported protocol
> ERROR: Could not find pull request info in 20260925-parlor-snowfield-6ca46312a610@spud
> 
> Can you change your 'insteadOf' setting to send this as a URL accepted
> by b4 in the future? I think an ssh://git@gitolite.kernel.org/ URL would
> work fine, but most people use https://git.kernel.org/

Ah shite, I know what's happened here.. I accidentally did "rm -rf linux"
instead of "rm -rf linux-temp" a few weeks ago and forgot that I used to
have things set up with different pull and push URLs. Things should be
fixed now:

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ tags/riscv-dt-fixes-for-v7.3-rc

for you to fetch changes up to 0f70fd6f4c1d6c1f2ea298d8dd07c4a4d5dff9af:

  riscv: dts: microchip: beaglev-fire: remove double definition of gpio interrupts (2026-09-08 19:18:19 +0100)

----------------------------------------------------------------
RISC-V devicetrees fixes for v7.3-rc

Microchip:
Remove double definition of interrupts on the BeagleV-Fire, which cause
the sensor to be associated the wrong plic interrupt.

Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

----------------------------------------------------------------
Conor Dooley (1):
      riscv: dts: microchip: beaglev-fire: remove double definition of gpio interrupts

 arch/riscv/boot/dts/microchip/mpfs-beaglev-fire.dts | 18 ------------------
 1 file changed, 18 deletions(-)

 Thanks for telling me, I keep running into stuff that I forgot I had
 configured. At least deleting my main repo instead of a worktree only
 lost me one branch with work that was easily recoverable...

 Thanks,
 Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-10-12  8:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 16:56 Conor Dooley
2026-10-12  8:10 ` Arnd Bergmann
2026-10-12  8:58   ` 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=20261012-ridden-paralysis-c095f7e937d7@spud \
    --to=conor@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®