public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Arnd Bergmann <arnd@arndb•de>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Thomas Hellstrom <thellstrom@vmware•com>,
	Dave Airlie <airlied@linux•ie>
Subject: linux-next: manual merge of the bkl-llseek tree with the drm tree
Date: Thu, 7 Oct 2010 14:53:09 +1100	[thread overview]
Message-ID: <20101007145309.0fb5dbe6.sfr@canb.auug.org.au> (raw)

Hi Arnd,

Today's linux-next merge of the bkl-llseek tree got a conflict in
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c between commit
7fbd721ad35f8ffec8d9a82e0e4b390cb6c9f4f7 ("drm/vmwgfx: Add new-style PM
hooks to improve hibernation behavior") from the drm tree and commit
dc880abef75e7c62c9048171f5112500f36a9244 ("drm: use noop_llseek") from
the bkl-llseek tree.

Just a trivial whitepsace change.  I fixed it up (see below) and can
carry the fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
index f2942b3,d237190..0000000
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
@@@ -899,16 -745,16 +899,17 @@@ static struct drm_driver driver = 
  #if defined(CONFIG_COMPAT)
  		 .compat_ioctl = drm_compat_ioctl,
  #endif
+ 		 .llseek = noop_llseek,
 -		 },
 +	},
  	.pci_driver = {
 -		       .name = VMWGFX_DRIVER_NAME,
 -		       .id_table = vmw_pci_id_list,
 -		       .probe = vmw_probe,
 -		       .remove = vmw_remove,
 -		       .suspend = vmw_pci_suspend,
 -		       .resume = vmw_pci_resume
 -		       },
 +		 .name = VMWGFX_DRIVER_NAME,
 +		 .id_table = vmw_pci_id_list,
 +		 .probe = vmw_probe,
 +		 .remove = vmw_remove,
 +		 .driver = {
 +			 .pm = &vmw_pm_ops
 +		 }
 +	 },
  	.name = VMWGFX_DRIVER_NAME,
  	.desc = VMWGFX_DRIVER_DESC,
  	.date = VMWGFX_DRIVER_DATE,

                 reply	other threads:[~2010-10-07  3:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20101007145309.0fb5dbe6.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=airlied@linux$(echo .)ie \
    --cc=arnd@arndb$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=thellstrom@vmware$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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