From: Greg KH <greg@kroah.com>
To: Rob Clark <rob.clark@linaro.org>
Cc: dri-devel@lists.freedesktop.org, patches@linaro.org
Subject: Re: [PATCH 1/2] drm/omap: drm API update: make fops struct const
Date: Mon, 12 Dec 2011 17:04:52 -0800 [thread overview]
Message-ID: <20111213010452.GA31721@kroah.com> (raw)
In-Reply-To: <CAF6AEGvCek25j7YJb1XH_3jzz3BFFmL1ukFN5vRCK2n0EVPqeA@mail.gmail.com>
On Mon, Dec 12, 2011 at 06:59:59PM -0600, Rob Clark wrote:
> On Mon, Dec 12, 2011 at 6:55 PM, Greg KH <greg@kroah.com> wrote:
> > On Mon, Dec 12, 2011 at 06:49:43PM -0600, Rob Clark wrote:
> >> From: Rob Clark <rob@ti.com>
> >>
> >> Update to reflect changes in:
> >> "Make the per-driver file_operations struct const"
> >
> > This one I could take today, no need for me to rely on the drm api
> > changes, right?
>
> I don't think so, at least not if you want it to compile ;-)
Doh, you are right, sorry about that.
> Previously the 'struct file_operations' was inline with the 'struct
> drm_driver' rather than a pointer. But if it it makes it easier for
> you to keep track I can keep a tree that you can pull from w/ a branch
> on top with the patches that depend on stuff coming in thru drm-next.
No, that would mix the two branches, and I can't do that, right?
So let's just wait for the drm-next branch to be merged with Linus, and
I'll hold onto these until then, ok?
thanks,
greg k-h
next prev parent reply other threads:[~2011-12-13 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 0:49 [PATCH 0/2] updates for drm API changes in drm-next Rob Clark
2011-12-13 0:49 ` [PATCH 1/2] drm/omap: drm API update: make fops struct const Rob Clark
2011-12-13 0:55 ` Greg KH
2011-12-13 0:59 ` Rob Clark
2011-12-13 1:04 ` Greg KH [this message]
2011-12-13 1:09 ` Rob Clark
2011-12-13 0:49 ` [PATCH 2/2] drm/omap: drm API update: addfb2 Rob Clark
2011-12-13 0:56 ` Greg KH
2011-12-13 1:02 ` Rob Clark
2011-12-14 2:18 ` Rob Clark
2011-12-14 18:45 ` Greg KH
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=20111213010452.GA31721@kroah.com \
--to=greg@kroah.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=patches@linaro.org \
--cc=rob.clark@linaro.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