All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Drew Fustini <fustini@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
	soc@kernel.org,
	 Alexandre Belloni <alexandre.belloni@bootlin.com>,
	 Arnd Bergmann <arnd@arndb.de>, Linus Walleij <linusw@kernel.org>,
	 Conor Dooley <conor@kernel.org>,
	 Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-kernel@vger.kernel.org,  linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V defconfig changes for v7.3
Date: Wed, 5 Aug 2026 08:42:39 -0600 (MDT)	[thread overview]
Message-ID: <42f428e2-8bb8-b14d-7ed3-e618bb467356@kernel.org> (raw)
In-Reply-To: <anKwl/5re7CMFTXF@x1>

On Tue, 4 Aug 2026, Drew Fustini wrote:

> Thank you for checking but this was already pulled by Arnd:
> https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?id=6495ae297ceb
> 
> It seems the patchwork reply had a narrow scope compared to my post:
> https://lore.kernel.org/all/178491121788.3229915.9040423834090729571.git-patchwork-notify@kernel.org/

Oh, okay, thanks.


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Drew Fustini <fustini@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
	soc@kernel.org,
	 Alexandre Belloni <alexandre.belloni@bootlin.com>,
	 Arnd Bergmann <arnd@arndb.de>, Linus Walleij <linusw@kernel.org>,
	 Conor Dooley <conor@kernel.org>,
	 Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-kernel@vger.kernel.org,  linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V defconfig changes for v7.3
Date: Wed, 5 Aug 2026 08:42:39 -0600 (MDT)	[thread overview]
Message-ID: <42f428e2-8bb8-b14d-7ed3-e618bb467356@kernel.org> (raw)
In-Reply-To: <anKwl/5re7CMFTXF@x1>

On Tue, 4 Aug 2026, Drew Fustini wrote:

> Thank you for checking but this was already pulled by Arnd:
> https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?id=6495ae297ceb
> 
> It seems the patchwork reply had a narrow scope compared to my post:
> https://lore.kernel.org/all/178491121788.3229915.9040423834090729571.git-patchwork-notify@kernel.org/

Oh, okay, thanks.


- Paul

  reply	other threads:[~2026-08-05 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 16:20 [GIT PULL] RISC-V defconfig changes for v7.3 Drew Fustini
2026-07-21 16:20 ` Drew Fustini
2026-07-24 16:40 ` patchwork-bot+linux-soc
2026-08-05  2:54 ` Paul Walmsley
2026-08-05  2:54   ` Paul Walmsley
2026-08-05  3:40   ` Drew Fustini
2026-08-05  3:40     ` Drew Fustini
2026-08-05 14:42     ` Paul Walmsley [this message]
2026-08-05 14:42       ` Paul Walmsley

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=42f428e2-8bb8-b14d-7ed3-e618bb467356@kernel.org \
    --to=pjw@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=conor@kernel.org \
    --cc=fustini@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=m.szyprowski@samsung.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.