public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@localhost.localdomain>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Manu Abraham <abraham.manu@gmail.com>
Subject: Re: [GIT PULL for v3.11-rc1] media patches for v3.11
Date: Sat, 6 Jul 2013 00:41:09 -0300 (BRT)	[thread overview]
Message-ID: <alpine.LFD.2.03.1307060037240.18850@localhost.localdomain> (raw)
In-Reply-To: <878v1kiw53.fsf@nemi.mork.no>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3330 bytes --]

On Fri, 5 Jul 2013, Bjørn Mork wrote:

> Mauro Carvalho Chehab <mchehab@infradead.org> writes:
>
>>  mode change 100755 => 100644 lib/build_OID_registry
>>  mode change 100755 => 100644 scripts/Lindent
>>  mode change 100755 => 100644 scripts/bloat-o-meter
>>  mode change 100755 => 100644 scripts/checkincludes.pl
>>  mode change 100755 => 100644 scripts/checkkconfigsymbols.sh
>>  mode change 100755 => 100644 scripts/checkpatch.pl
>>  mode change 100755 => 100644 scripts/checkstack.pl
>>  mode change 100755 => 100644 scripts/checksyscalls.sh
>>  mode change 100755 => 100644 scripts/checkversion.pl
>>  mode change 100755 => 100644 scripts/cleanfile
>>  mode change 100755 => 100644 scripts/cleanpatch
>>  mode change 100755 => 100644 scripts/coccicheck
>>  mode change 100755 => 100644 scripts/config
>>  mode change 100755 => 100644 scripts/decodecode
>>  mode change 100755 => 100644 scripts/depmod.sh
>>  mode change 100755 => 100644 scripts/diffconfig
>>  mode change 100755 => 100644 scripts/extract-ikconfig
>>  mode change 100755 => 100644 scripts/extract-vmlinux
>>  mode change 100755 => 100644 scripts/get_maintainer.pl
>>  mode change 100755 => 100644 scripts/gfp-translate
>>  mode change 100755 => 100644 scripts/headerdep.pl
>>  mode change 100755 => 100644 scripts/headers.sh
>>  mode change 100755 => 100644 scripts/kconfig/check.sh
>>  mode change 100755 => 100644 scripts/kconfig/merge_config.sh
>>  mode change 100755 => 100644 scripts/kernel-doc
>>  mode change 100755 => 100644 scripts/makelst
>>  mode change 100755 => 100644 scripts/mkcompile_h
>>  mode change 100755 => 100644 scripts/mkuboot.sh
>>  mode change 100755 => 100644 scripts/namespace.pl
>>  mode change 100755 => 100644 scripts/package/mkspec
>>  mode change 100755 => 100644 scripts/patch-kernel
>>  mode change 100755 => 100644 scripts/recordmcount.pl
>>  mode change 100755 => 100644 scripts/setlocalversion
>>  mode change 100755 => 100644 scripts/show_delta
>>  mode change 100755 => 100644 scripts/sign-file
>>  mode change 100755 => 100644 scripts/tags.sh
>>  mode change 100755 => 100644 scripts/ver_linux
>>  mode change 100755 => 100644 tools/hv/hv_get_dhcp_info.sh
>>  mode change 100755 => 100644 tools/hv/hv_get_dns_info.sh
>>  mode change 100755 => 100644 tools/hv/hv_set_ifconfig.sh
>>  mode change 100755 => 100644 tools/nfsd/inject_fault.sh
>>  mode change 100755 => 100644 tools/perf/python/twatch.py
>>  mode change 100755 => 100644 tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/EventClass.py
>>  mode change 100755 => 100644 tools/perf/scripts/python/bin/net_dropmonitor-record
>>  mode change 100755 => 100644 tools/perf/scripts/python/bin/net_dropmonitor-report
>>  mode change 100755 => 100644 tools/perf/scripts/python/net_dropmonitor.py
>>  mode change 100755 => 100644 tools/perf/util/PERF-VERSION-GEN
>>  mode change 100755 => 100644 tools/perf/util/generate-cmdlist.sh
>>  mode change 100755 => 100644 tools/power/cpupower/utils/version-gen.sh
>>  mode change 100755 => 100644 tools/testing/ktest/compare-ktest-sample.pl
>>  mode change 100755 => 100644 tools/testing/ktest/ktest.pl
>
>
> You didn't really mean to do that, did you?

No, those changes were incidental. It were caused by a bad script
that were meant to just replace my e-mail.

I'll fix it.

Thanks for pointing it!

Regards,
Mauro

      reply	other threads:[~2013-07-06  3:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 14:40 [GIT PULL for v3.11-rc1] media patches for v3.11 Mauro Carvalho Chehab
2013-07-05 20:34 ` Bjørn Mork
2013-07-06  3:41   ` Mauro Carvalho Chehab [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=alpine.LFD.2.03.1307060037240.18850@localhost.localdomain \
    --to=mchehab@localhost.localdomain \
    --cc=abraham.manu@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bjorn@mork.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=mchehab@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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