On Tue, Jul 02, 2013 at 03:32:34PM +0530, Viresh Kumar wrote: > On 2 July 2013 15:18, Mark Brown <broonie@xxxxxxxxxx> wrote: > > This doesn't apply terribly easily, the patch is corrupt and appears to > > be based on something other than what's in -next so neither git am nor > > patch can figure out how to apply it. > Two things, > - I rebased my patch now against latest linux-next/master and it applied > cleanly. > - Somehow one of my changes to include/linux/cpufreq.h didn't get commited > Try attached patch now and it should really work.. That seems to work, yes. Tested-by: Mark Brown <broonie@xxxxxxxxxx> > I am using gmail for replying to mails from office which corrupts mails. And > I can't use other mail clients from office, firewall issues. If you're forced to do stuff like that then don't include the patch in the body of the e-mail, it just makes everything worse. Not only is the copy in the body of the e-mail broken but there's now two copies so tools like git am get even more upset as they may potentially see some of the hunks twice.
Attachment:
signature.asc
Description: Digital signature
