From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Ameya Palande <ameya.palande@nokia.com>
Subject: Re: [PATCH 02/10] dsp-bridge: deh: trivial cleanups
Date: Tue, 23 Mar 2010 19:04:21 -0500 [thread overview]
Message-ID: <4BA95705.6090103@ti.com> (raw)
In-Reply-To: <1269379542-11892-3-git-send-email-felipe.contreras@gmail.com>
On 3/23/2010 4:25 PM, Felipe Contreras wrote:
> Mostly white-space formatting.
>
Most of this white space changes were made because of rules defined when
executing Lindent, if there is an agreement that this Lindent changes
are bringing more trouble I think we should roll them back instead of
manually fixing all of them.
Regards,
Omar
next prev parent reply other threads:[~2010-03-24 0:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 21:25 [PATCH 00/10] dsp-bridge: deh: general cleanups Felipe Contreras
2010-03-23 21:25 ` [PATCH 01/10] dsp-bridge: deh: remove obvious comments Felipe Contreras
2010-03-23 21:25 ` [PATCH 02/10] dsp-bridge: deh: trivial cleanups Felipe Contreras
2010-03-24 0:04 ` Omar Ramirez Luna [this message]
2010-03-23 21:25 ` [PATCH 03/10] dsp-bridge: deh: remove unnecessary casts Felipe Contreras
2010-03-23 21:25 ` [PATCH 04/10] dsp-bridge: deh: improve logging stuff Felipe Contreras
2010-03-23 21:25 ` [PATCH 05/10] dsp-bridge: deh: report mmu faults as errors Felipe Contreras
2010-03-23 21:25 ` [PATCH 06/10] dsp-bridge: deh: decrease nesting levels Felipe Contreras
2010-03-23 21:25 ` [PATCH 07/10] dsp-bridge: deh: fix obvious return codes Felipe Contreras
2010-03-23 21:25 ` [PATCH 08/10] dsp-bridge: deh: reorganize create() Felipe Contreras
2010-03-23 21:25 ` [PATCH 09/10] dsp-bridge: deh: fix hdeh_mgr silliness Felipe Contreras
2010-03-23 21:25 ` [PATCH 10/10] dsp-bridge: deh: fix dummy_va_addr Felipe Contreras
2010-04-15 12:12 ` [PATCH 00/10] dsp-bridge: deh: general cleanups Felipe Contreras
2010-04-19 20:37 ` Omar Ramirez Luna
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=4BA95705.6090103@ti.com \
--to=omar.ramirez@ti.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=linux-omap@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.