From: Jiri Kosina <jikos@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
intel-gfx@lists.freedesktop.org, ville.syrjala@linux.intel.com,
linux-input@vger.kernel.org,
"Daniel Vetter" <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v2 11/14] HID: picoLCD: constify fb ops
Date: Sun, 8 Dec 2019 01:07:02 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.1912080106260.4603@cbobk.fhfr.pm> (raw)
In-Reply-To: <871rtji02a.fsf@intel.com>
On Thu, 5 Dec 2019, Jani Nikula wrote:
> >> Now that the fbops member of struct fb_info is const, we can start
> >> making the ops const as well.
> >>
> >> v2: fix typo (Christophe de Dinechin)
> >
> > Fine with me.
> > I don't think going through drm-misc would trigger any conflict, but
> > adding Jiri to CC for the case there was any preference.
> >
> > Acked-by: Bruno Prémont <bonbons@linux-vserver.org>
>
> No response, may I proceed with merging this through drm-misc please?
I have been off the grid the past week, sorry for belated response. Feel
free to add
Acked-by: Jiri Kosina <jkosina@suse.cz>
and take it through your tree.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2019-12-08 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 10:29 [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Jani Nikula
2019-11-29 10:29 ` [PATCH v2 11/14] HID: picoLCD: constify fb ops Jani Nikula
2019-12-02 8:40 ` Bruno Prémont
2019-12-05 9:38 ` Jani Nikula
2019-12-08 0:07 ` Jiri Kosina [this message]
2019-11-29 15:40 ` [PATCH v2 00/14] video, drm, etc: constify fbops in struct fb_info Daniel Vetter
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=nycvar.YFH.7.76.1912080106260.4603@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=bonbons@linux-vserver.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/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).