From: Joe Perches <joe@perches.com>
To: Jiri Kosina <trivial@kernel.org>,
drbd-dev@lists.linbit.com, dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
devel@driverdev.osuosl.org, alsa-devel@alsa-project.org
Subject: [Trivial PATCH 0/5] treewide: Use angle brackets for system includes
Date: Fri, 3 Jun 2011 02:28:45 -0700 [thread overview]
Message-ID: <cover.1307092588.git.joe@perches.com> (raw)
Just neatening.
Joe Perches (5):
drbd: Use angle brackets for system includes
drm: Use angle brackets for system includes
aix94xx: Use angle brackets for system includes
ALSA: asihpi: Use angle brackets for system includes
staging: msm: Use angle brackets for system includes
drivers/block/drbd/drbd_int.h | 2 +-
drivers/block/drbd/drbd_nl.c | 4 ++--
drivers/gpu/drm/drm_ioctl.c | 2 +-
drivers/gpu/drm/i915/i915_gem_tiling.c | 4 ++--
drivers/gpu/drm/nouveau/nouveau_drv.h | 10 +++++-----
drivers/gpu/drm/ttm/ttm_agp_backend.c | 6 +++---
drivers/gpu/drm/ttm/ttm_bo.c | 6 +++---
drivers/gpu/drm/ttm/ttm_bo_manager.c | 6 +++---
drivers/gpu/drm/ttm/ttm_bo_util.c | 4 ++--
drivers/gpu/drm/ttm/ttm_execbuf_util.c | 6 +++---
drivers/gpu/drm/ttm/ttm_lock.c | 4 ++--
drivers/gpu/drm/ttm/ttm_memory.c | 6 +++---
drivers/gpu/drm/ttm/ttm_module.c | 2 +-
drivers/gpu/drm/ttm/ttm_object.c | 4 ++--
drivers/gpu/drm/ttm/ttm_page_alloc.c | 4 ++--
drivers/gpu/drm/ttm/ttm_tt.c | 8 ++++----
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c | 4 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 8 ++++----
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 12 ++++++------
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 4 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_gmr.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_gmrid_manager.c | 6 +++---
drivers/gpu/drm/vmwgfx/vmwgfx_overlay.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_resource.c | 4 ++--
drivers/scsi/aic94xx/aic94xx_dump.c | 2 +-
drivers/staging/msm/ebi2_l2f.c | 2 +-
drivers/staging/msm/ebi2_tmd20.c | 2 +-
drivers/staging/msm/mddihost.h | 2 +-
drivers/staging/msm/mdp_ppp.c | 2 +-
drivers/staging/msm/mdp_ppp_v20.c | 2 +-
drivers/staging/msm/mdp_ppp_v31.c | 2 +-
drivers/staging/msm/msm_fb.h | 2 +-
include/drm/ttm/ttm_bo_driver.h | 12 ++++++------
include/drm/ttm/ttm_execbuf_util.h | 2 +-
include/drm/ttm/ttm_lock.h | 2 +-
include/linux/drbd_tag_magic.h | 2 +-
sound/pci/asihpi/hpidspcd.c | 2 +-
39 files changed, 80 insertions(+), 80 deletions(-)
--
1.7.5.rc3.dirty
next reply other threads:[~2011-06-03 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 9:28 Joe Perches [this message]
2011-06-03 9:28 ` [Trivial PATCH 1/5] drbd: Use angle brackets for system includes Joe Perches
2011-06-03 9:28 ` [Trivial PATCH 2/5] drm: " Joe Perches
2011-06-03 17:35 ` Keith Packard
2011-06-03 9:28 ` [Trivial PATCH 3/5] aix94xx: " Joe Perches
2011-06-03 9:28 ` [Trivial PATCH 4/5] ALSA: asihpi: " Joe Perches
2011-06-03 9:47 ` Takashi Iwai
2011-06-03 9:28 ` [Trivial PATCH 5/5] staging: msm: " Joe Perches
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=cover.1307092588.git.joe@perches.com \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=devel@driverdev.osuosl.org \
--cc=drbd-dev@lists.linbit.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox