From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [GIT PULL] fbdev fixes and updates for v6.7-rc3
Date: Sun, 26 Nov 2023 17:42:08 +0100 [thread overview]
Message-ID: <e47c68f7-20ee-487a-9c94-61eeeb014333@gmx.de> (raw)
In-Reply-To: <CAHk-=wiR5yLK6-n5p=F97unF1bf3DuPdGcv0MZcO51aiik4T0w@mail.gmail.com>
On 11/26/23 17:29, Linus Torvalds wrote:
> On Sat, 25 Nov 2023 at 22:58, Helge Deller <deller@gmx.de> wrote:
>>
>> please pull some small fbdev fixes for 6.7-rc3.
>
> These all seem to be pure cleanups, not bug fixes.
Well, at least:
- fbdev: imxfb: fix left margin setting
is a bug fix,
and:
- fbdev: fsl-diu-fb: Fix sparse warning due to virt_to_phys() prototype change
pops up in in multiple sparse reports.
> Please resend during the merge window.
I'll do.
Thanks!
Helge
prev parent reply other threads:[~2023-11-26 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 6:58 [GIT PULL] fbdev fixes and updates for v6.7-rc3 Helge Deller
2023-11-26 16:29 ` Linus Torvalds
2023-11-26 16:42 ` Helge Deller [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=e47c68f7-20ee-487a-9c94-61eeeb014333@gmx.de \
--to=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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