From: "Arnd Bergmann" <arnd@arndb.de>
To: Mike Rapoport <rppt@kernel.org>
Cc: Dave Airlie <airlied@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Helge Deller <deller@gmx.de>, Matt Turner <mattst88@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
x86@kernel.org, dri-devel@lists.freedesktop.org,
linux-alpha@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/2] char/agp: consolidate asm/agp.h
Date: Mon, 27 Feb 2023 21:04:04 +0100 [thread overview]
Message-ID: <5de30963-9be9-4e87-a696-7a642d92630f@app.fastmail.com> (raw)
In-Reply-To: <20230212084611.1311177-1-rppt@kernel.org>
On Sun, Feb 12, 2023, at 09:46, Mike Rapoport wrote:
> From: "Mike Rapoport (IBM)" <rppt@kernel.org>
>
> asm/agp.h is duplicated in several architectures, with x86 being the
> only instance that differs from the rest.
>
> Introduce asm-generic/agp.h and use it instead of per-architecture
> headers for the most cases.
>
> I believe that asm-generic is the best tree to pick up this patches.
>
> Mike Rapoport (IBM) (2): char/agp: consolidate
> {alloc,free}_gatt_pages() char/agp: introduce asm-generic/agp.h
Hi Mike,
It looks like I wrote an email saying I merged these two patches,
but never actually sent it out. Not sure if you found out another
way, but this was part of the asm-generic tree for 6.3 and is now
merged upstream.
Thanks for the cleanup,
Arnd
prev parent reply other threads:[~2023-02-27 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 8:46 [PATCH 0/2] char/agp: consolidate asm/agp.h Mike Rapoport
2023-02-12 8:46 ` [PATCH 1/2] char/agp: consolidate {alloc,free}_gatt_pages() Mike Rapoport
2023-02-12 8:46 ` [PATCH 2/2] char/agp: introduce asm-generic/agp.h Mike Rapoport
2023-02-27 20:04 ` Arnd Bergmann [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=5de30963-9be9-4e87-a696-7a642d92630f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=airlied@redhat.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mattst88@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=rppt@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).