From: Daniel Vetter <daniel@ffwll.ch>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Gal Pressman <galpress@amazon.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"open list:DMA BUFFER SHARING FRAMEWORK"
<linux-media@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: Couple of documentation typo fixes
Date: Thu, 23 Apr 2020 13:46:35 +0200 [thread overview]
Message-ID: <CAKMK7uGTP93tbpsZhc1On2ka+YiVhwHk32cWHEdvS5O5DGODTg@mail.gmail.com> (raw)
In-Reply-To: <20200421103236.4b64155c@lwn.net>
On Tue, Apr 21, 2020 at 6:32 PM Jonathan Corbet <corbet@lwn.net> wrote:
>
> On Tue, 21 Apr 2020 14:38:37 +0200
> Daniel Vetter <daniel@ffwll.ch> wrote:
>
> > On Mon, Apr 20, 2020 at 05:00:59PM -0600, Jonathan Corbet wrote:
> > > On Mon, 20 Apr 2020 10:41:15 +0300
> > > Gal Pressman <galpress@amazon.com> wrote:
> > >
> > > > Fix a couple of typos: "as" -> "has" and "int" -> "in".
> > > >
> > > > Signed-off-by: Gal Pressman <galpress@amazon.com>
> > >
> > > Applied, thanks.
> >
> > Also applied to drm-misc-next, the dma-buf stuff is maintained as part of
> > drm. And maybe I actually get around to doing the doc polish for all
> > things dma-buf that I've been promised to do since months :-)
>
> I actually looked for it in linux-next before applying, but didn't (and
> don't) see it there...?
I only spotted the patch after I've seen your notification, so it was
indeed not there back then. But now it should be there:
commit 776d58823a60c689816972b51100cb322a0834ce (HEAD ->
drm-misc-next, drm-misc/for-linux-next, drm-misc/drm-misc-next)
Author: Gal Pressman <galpress@amazon.com>
Date: Mon Apr 20 10:41:15 2020 +0300
dma-buf: Couple of documentation typo fixes
drm-misc/for-linux-next is included in linux-next (we have some
special branches for linux-next because of some different rules than
usual for our committers). Latest linux-next also seems to have it by
now.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2020-04-23 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:41 [PATCH] dma-buf: Couple of documentation typo fixes Gal Pressman
2020-04-20 23:00 ` Jonathan Corbet
2020-04-21 12:38 ` Daniel Vetter
2020-04-21 16:32 ` Jonathan Corbet
2020-04-23 11:46 ` Daniel Vetter [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=CAKMK7uGTP93tbpsZhc1On2ka+YiVhwHk32cWHEdvS5O5DGODTg@mail.gmail.com \
--to=daniel@ffwll.ch \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=galpress@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.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 NNTP newsgroup(s).