From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Greg KH <greg@kroah.com>, Marcel Ziswiler <marcel@ziswiler.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
dri-devel@lists.freedesktop.org,
open list <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Maxime Ripard <mripard@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Linus Walleij <linus.walleij@linaro.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: [PATCH v2] drm: import DMA_BUF module namespace
Date: Mon, 1 Nov 2021 08:25:43 +1100 [thread overview]
Message-ID: <20211101082543.0e47af76@canb.auug.org.au> (raw)
In-Reply-To: <eadfa89d-1c39-be25-abaf-4150396e1024@suse.de>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
Hi Thomas,
On Sun, 31 Oct 2021 19:13:17 +0100 Thomas Zimmermann <tzimmermann@suse.de> wrote:
>
> No no, don't worry. I meant 'import' as in 'git remote add
> linux-next'. I was actually complaining that the provided fix was not
> against a DRM tree.
Phew! :-)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-10-31 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 21:25 [PATCH v2] drm: import DMA_BUF module namespace Marcel Ziswiler
2021-10-29 18:51 ` Thomas Zimmermann
2021-10-31 2:21 ` Stephen Rothwell
2021-10-31 3:30 ` Stephen Rothwell
2021-10-31 18:13 ` Thomas Zimmermann
2021-10-31 21:25 ` Stephen Rothwell [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=20211101082543.0e47af76@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@bootlin.com \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@ziswiler.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.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).