From: Liam Girdwood <lrg@kernel.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] regulator: tps65023: patch updates
Date: Mon, 08 Aug 2011 17:39:36 +0100 [thread overview]
Message-ID: <1312821576.3316.2.camel@odin> (raw)
In-Reply-To: <1312457632-27075-1-git-send-email-marcus.folkesson@gmail.com>
On Thu, 2011-08-04 at 13:33 +0200, Marcus Folkesson wrote:
> I'm currently fighting with my email-client (Mark, sorry for the draft just sent), but this should be proper in both formatting and email-list.
>
>
> Changes from previous patches:
> * Split up [PATCH 1/3] into two seperate patches ([PATCH [1-2]/4])
> * Declared tps_driver_data.info as const for avoiding awkward typecastings
> * Removed table-length structs and uses tps->table_len instead. (As Axel Lin suggested in lkml)
>
I've applied patch 1. 3 & 4 don't apply against -next.
Can you resend and add Mark's Acks to the relevant patches.
Thanks
Liam
prev parent reply other threads:[~2011-08-08 16:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 11:33 [PATCH 0/4] regulator: tps65023: patch updates Marcus Folkesson
2011-08-04 11:33 ` [PATCH 1/4] regulator: tps65023: Fixes i2c configuration issues Marcus Folkesson
2011-08-04 12:13 ` Mark Brown
2011-08-04 13:39 ` Marcus Folkesson
2011-08-04 13:40 ` Mark Brown
2011-08-04 11:33 ` [PATCH 2/4] regulator: tps65023: Set missing bit for update core-voltage Marcus Folkesson
2011-08-04 12:26 ` Mark Brown
2011-08-04 11:33 ` [PATCH 3/4] regulator: tps65023: Setting correct core regulator for tps65021 Marcus Folkesson
2011-08-04 12:26 ` Mark Brown
2011-08-04 11:33 ` [PATCH 4/4] regulator: tps65023: Added support for the similiar TPS65020 chip Marcus Folkesson
2011-08-04 12:27 ` Mark Brown
2011-08-08 16:39 ` Liam Girdwood [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=1312821576.3316.2.camel@odin \
--to=lrg@kernel.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=marcus.folkesson@gmail.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