From: Christoph Hellwig <hch@lst.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@lst.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"David S. Miller" <davem@davemloft.net>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
sparclinux <sparclinux@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/3] fbdev/sbuslib: remove FBIOSCURSOR/FBIOGCURSOR leftovers
Date: Wed, 07 Oct 2020 08:59:11 +0000 [thread overview]
Message-ID: <20201007085911.GA17356@lst.de> (raw)
In-Reply-To: <CAK8P3a0UHEsND+vJjhtj2GKQpMjMCqD55vQ9+2u-SCrThe3wTw@mail.gmail.com>
On Wed, Oct 07, 2020 at 10:54:19AM +0200, Arnd Bergmann wrote:
> On Wed, Oct 7, 2020 at 9:44 AM Christoph Hellwig <hch@lst.de> wrote:
> >
> > There are no actual implementations of FBIOSCURSOR/FBIOGCURSOR left, so
> > don't bother with a compat handler for it, and remove the remaining
> > definitions as well.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> I had submitted a similar patch earlier, and Sam Ravnborg applied it to the
> drm-misc tree, but it doesn't seem to be in linux-next, so I don't know
> what the state is.
>
> My version only removed the compat handling, not the data structures,
> so I'm happy to see your version used instead if mine got lost.
Oh, sorry. I thought in your summary you decided to give up on
the sbuslib ones.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@lst.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"David S. Miller" <davem@davemloft.net>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
sparclinux <sparclinux@vger.kernel.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/3] fbdev/sbuslib: remove FBIOSCURSOR/FBIOGCURSOR leftovers
Date: Wed, 7 Oct 2020 10:59:11 +0200 [thread overview]
Message-ID: <20201007085911.GA17356@lst.de> (raw)
In-Reply-To: <CAK8P3a0UHEsND+vJjhtj2GKQpMjMCqD55vQ9+2u-SCrThe3wTw@mail.gmail.com>
On Wed, Oct 07, 2020 at 10:54:19AM +0200, Arnd Bergmann wrote:
> On Wed, Oct 7, 2020 at 9:44 AM Christoph Hellwig <hch@lst.de> wrote:
> >
> > There are no actual implementations of FBIOSCURSOR/FBIOGCURSOR left, so
> > don't bother with a compat handler for it, and remove the remaining
> > definitions as well.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> I had submitted a similar patch earlier, and Sam Ravnborg applied it to the
> drm-misc tree, but it doesn't seem to be in linux-next, so I don't know
> what the state is.
>
> My version only removed the compat handling, not the data structures,
> so I'm happy to see your version used instead if mine got lost.
Oh, sorry. I thought in your summary you decided to give up on
the sbuslib ones.
next prev parent reply other threads:[~2020-10-07 8:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 7:44 fbdev sbuslib cleanups Christoph Hellwig
2020-10-07 7:44 ` Christoph Hellwig
2020-10-07 7:44 ` [PATCH 1/3] fbdev/sbuslib: remove FBIOSCURSOR/FBIOGCURSOR leftovers Christoph Hellwig
2020-10-07 7:44 ` Christoph Hellwig
2020-10-07 8:05 ` Geert Uytterhoeven
2020-10-07 8:05 ` Geert Uytterhoeven
2020-10-07 8:54 ` Arnd Bergmann
2020-10-07 8:54 ` Arnd Bergmann
2020-10-07 8:59 ` Christoph Hellwig [this message]
2020-10-07 8:59 ` Christoph Hellwig
2020-10-07 9:28 ` Arnd Bergmann
2020-10-07 9:28 ` Arnd Bergmann
2020-10-07 10:40 ` Christoph Hellwig
2020-10-07 10:40 ` Christoph Hellwig
2020-10-07 11:07 ` Arnd Bergmann
2020-10-07 11:07 ` Arnd Bergmann
2020-10-07 15:41 ` Sam Ravnborg
2020-10-07 15:41 ` Sam Ravnborg
2020-10-07 7:44 ` [PATCH 2/3] fbdev/sbuslib: refactor sbusfb_ioctl_helper Christoph Hellwig
2020-10-07 7:44 ` Christoph Hellwig
2020-10-07 7:44 ` [PATCH 3/3] fbdev/sbuslib: avoid compat_alloc_user_space in fbiogetputcmap Christoph Hellwig
2020-10-07 7:44 ` Christoph Hellwig
2020-10-07 9:14 ` Arnd Bergmann
2020-10-07 9:14 ` Arnd Bergmann
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=20201007085911.GA17356@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=sam@ravnborg.org \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.