From: Tony Lindgren <tony@atomide.com>
To: Komal Shah <komal.shah802003@gmail.com>
Cc: linux-omap-open-source <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: omap-alsa-aic23.c cleanup. No code change
Date: Mon, 11 Dec 2006 13:41:56 -0800 [thread overview]
Message-ID: <20061211214155.GH6693@atomide.com> (raw)
In-Reply-To: <3a5b1be00612030949p33bb4b96r537524fadcd10c17@mail.gmail.com>
* Komal Shah <komal.shah802003@gmail.com> [061203 09:50]:
> --
> ---Komal Shah
> http://komalshah.blogspot.com
> From e00b82a90c3086f596d5478e57249cf86e056b33 Mon Sep 17 00:00:00 2001
> From: Komal Shah <komal_shah802003@yahoo.com>
> Date: Sun, 3 Dec 2006 23:11:29 +0530
> Subject: [PATCH] ARM: OMAP: omap-alsa-aic23.c cleanup. No code change.
>
> - whitespace removal.
> - Follow 80 line rule. Still few places left.
This one does not seem to apply, can you please refresh?
Regards,
Tony
prev parent reply other threads:[~2006-12-11 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 17:49 [PATCH] ARM: OMAP: omap-alsa-aic23.c cleanup. No code change Komal Shah
2006-12-11 21:41 ` Tony Lindgren [this message]
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=20061211214155.GH6693@atomide.com \
--to=tony@atomide.com \
--cc=komal.shah802003@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
/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