All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jhnikula@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org, linuxtv-commits@linuxtv.org,
	Eduardo Valentin <eduardo.valentin@nokia.com>
Subject: Re: [git:v4l-dvb/v2.6.37] [media] radio-si4713: Add regulator framework support
Date: Fri, 29 Oct 2010 17:26:01 +0300	[thread overview]
Message-ID: <20101029172601.fdf7ed07.jhnikula@gmail.com> (raw)
In-Reply-To: <4CCAD21A.9040100@redhat.com>

On Fri, 29 Oct 2010 11:54:34 -0200
Mauro Carvalho Chehab <mchehab@redhat.com> wrote:

> I had to remove it from my queue, as the patch broke compilation:
> 
> 	http://git.linuxtv.org/media_tree.git?a=commit;h=350df81ebaccc651fa4dfad27738db958e067ded
> 
> What's the sense of adding a patch that breaks a driver?
> 
> Even assuming that you would later send a patch fixing it, there are still some problems:
> 
> 1) A latter patch will break git bisect;
> 2) A broken driver means that I can't test anymore if there are any other problems on other
>    drivers.
> 
> So, please test your patches against breakages, before sending them to me.
> 
Oh shit, true, my fault. I definitely forgot one file from git commit
but luckily I had the diff file around that I used in testing instead
of the commit I sent...

Sorry the hassle and thanks for letting me know, I'll send an update
in a minute.


-- 
Jarkko

  reply	other threads:[~2010-10-29 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1P7ZwW-0003bq-Uv@www.linuxtv.org>
2010-10-29  6:29 ` [git:v4l-dvb/v2.6.37] [media] radio-si4713: Add regulator framework support Jarkko Nikula
2010-10-29 13:54   ` Mauro Carvalho Chehab
2010-10-29 14:26     ` Jarkko Nikula [this message]
2010-10-29 14:31       ` [PATCH] V4L/DVB: " Jarkko Nikula

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=20101029172601.fdf7ed07.jhnikula@gmail.com \
    --to=jhnikula@gmail.com \
    --cc=eduardo.valentin@nokia.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linuxtv-commits@linuxtv.org \
    --cc=mchehab@redhat.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 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.