All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: Jean Delvare <khali@linux-fr.org>,
	linux-media@vger.kernel.org, linuxtv-commits-bounces@linuxtv.org,
	linuxtv-commits@linuxtv.org,
	"Eric W.Biederman" <ebiederm@xmission.com>
Subject: Re: [git:v4l-dvb/master] sysfs: sysfs_sd_setattr set iattrs	unconditionally
Date: Sat, 06 Mar 2010 14:11:27 -0300	[thread overview]
Message-ID: <4B928CBF.8070807@redhat.com> (raw)
In-Reply-To: <20100306161251.GA23287@suse.de>

Greg KH wrote:
> On Sat, Mar 06, 2010 at 05:06:55PM +0100, Jean Delvare wrote:
>> Err, what's happening here? I can't see any chmod call in any V4L or DVB
>> driver, so why would this patch matter there? And we will get this fix
>> through Linus' tree anyway, so why bother at all? I'm puzzled.
> 
> I'm confused too, I got a bunch of these, for patches that seem to be in
> Linus's tree already.  Did a script go haywire?

Sorry!

There's an post receive hook script that sends an email to the patch author/SOB's 
for the new patches added at v4l-dvb git tree. Unfortunately, the git mailbomb 
script did something wrong: it handled badly all the upstream patches 
that  were merged back on git. I'll need to figure out a way for it to exclude 
patches that got merged from the normal posts.

For now, I've disabled it and removed the patches that were on the queue.

-- 

Cheers,
Mauro

      reply	other threads:[~2010-03-06 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Nnuwt-0000VK-9b@www.linuxtv.org>
     [not found] ` <20100306170655.03d97556@hyperion.delvare>
2010-03-06 16:12   ` [git:v4l-dvb/master] sysfs: sysfs_sd_setattr set iattrs unconditionally Greg KH
2010-03-06 17:11     ` 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=4B928CBF.8070807@redhat.com \
    --to=mchehab@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --cc=khali@linux-fr.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxtv-commits-bounces@linuxtv.org \
    --cc=linuxtv-commits@linuxtv.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.