From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Taylor Hutt <thutt@chromium.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CHROMIUM: ASoC: Remove 'const' modifiers which cause warnings during compilation.
Date: Tue, 10 May 2011 22:03:20 +0100 [thread overview]
Message-ID: <20110510210319.GA17589@sirena.org.uk> (raw)
In-Reply-To: <1305054860-16054-1-git-send-email-thutt@chromium.org>
On Tue, May 10, 2011 at 12:14:20PM -0700, Taylor Hutt wrote:
> This change removes a warning produced when 'const * const' values
> are assigned to a 'const **'.
>
> These code being modified originally came from these two commits:
>
> http://git.kernel.org/?p=linux/kernel/git/broonie/sound-2.6.git;a=commit;h=82a5a936f6dea13849d93a2899a9b7294a8db336
> http://git.kernel.org/?p=linux/kernel/git/broonie/sound-2.6.git;a=commit;h=dad31ec133adb20c8fd10bfd9379da3f08b8721e
>
> Change-Id: I964ff6d24aafe78c2db7002abfd03b9069db9687
> Signed-off-by: Taylor Hutt <thutt@chromium.org>
This is already fixed in -next.
Please follow the patch submission procedure in SubmittingPatches, in
particular:
- Send patches to the relevant maintainers and mailing lists.
- Don't include "CHROMIUM" or other local things like gerritt artifacts
in your changelog.
If you don't send patches to the maintainers there's a reasonable chance
they'll never see them, and the changelog stuff is just irrelevant and
makes it harder to apply the patch as the maintainer has to manually
remove them.
prev parent reply other threads:[~2011-05-10 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:14 [PATCH] CHROMIUM: ASoC: Remove 'const' modifiers which cause warnings during compilation Taylor Hutt
2011-05-10 21:03 ` Mark Brown [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=20110510210319.GA17589@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thutt@chromium.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