All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: ak5386: Add regulators to documentation and fix sparse warning
Date: Wed, 18 Jun 2014 17:12:49 +0200	[thread overview]
Message-ID: <53A1AC71.7070403@zonque.org> (raw)
In-Reply-To: <20140329101708.GH21628@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 598 bytes --]

On 03/29/2014 11:17 AM, Mark Brown wrote:
> On Fri, Mar 28, 2014 at 07:05:04PM +0100, Daniel Mack wrote:
>> Document the newly added regulators to the DT binding document.
>>
>> Also, "static const char const *x" is not identical to "static const
>> char * const x", which sparse now complains about. Fix it.
> 
> Applied, though this should really have been two patches as there's no
> overlap.
> 

Hmm, for some reason, this patch didn't make it to mainline yet. Same
for another one that patches the same file which I sent the same day.
Want me to resend?


Thanks,
Daniel



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2014-06-18 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 18:05 [PATCH 1/2] ASoC: ak5386: Add regulators to documentation and fix sparse warning Daniel Mack
2014-03-28 18:05 ` [PATCH 2/2] ASoC: ak4104: Add regulator to documentation Daniel Mack
2014-03-29 10:17   ` Mark Brown
2014-03-29 10:17 ` [PATCH 1/2] ASoC: ak5386: Add regulators to documentation and fix sparse warning Mark Brown
2014-06-18 15:12   ` Daniel Mack [this message]
2014-06-18 17:54     ` Mark Brown

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=53A1AC71.7070403@zonque.org \
    --to=daniel@zonque.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@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.