All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Alfredo Jesús Delaiti" <alfredodelaiti@netscape.net>
Cc: linux-media@vger.kernel.org
Subject: Re: How I must report that a driver has been broken?
Date: Sun, 13 May 2012 07:50:50 +0200	[thread overview]
Message-ID: <4FAF4BBA.9090904@redhat.com> (raw)
In-Reply-To: <4FAEB948.7080800@netscape.net>

Hi,

On 05/12/2012 09:26 PM, Alfredo Jesús Delaiti wrote:
> Hi
>
> Thanks for your response Hans and Patrick
>
> Maybe I doing wrong this, because it reports twice:
>
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg45199.html
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg44846.html

In your last message you indicate that you've found the patch causing it,
and that you were looking into figuring which bit of the patch actually
breaks things, so I guess people reading the thread were / are
waiting for you to follow up on it with the results of your attempts
to further isolate the cause.

What I were do if I were you is send a mail directly to the author
of the patch causing the problems, with what you've discovered
about the problem sofar in there, and put the list in the CC.

Regards,

Hans

  parent reply	other threads:[~2012-05-13  5:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  4:26 How I must report that a driver has been broken? Alfredo Jesús Delaiti
2012-05-12  8:17 ` Hans de Goede
2012-05-12 19:26   ` Alfredo Jesús Delaiti
2012-05-13  0:29     ` Patrick Dickey
2012-05-13  5:50     ` Hans de Goede [this message]
2012-05-14  4:51       ` Devin Heitmueller
2012-05-18 14:15         ` Alfredo Jesús Delaiti
2012-05-18 14:26           ` Devin Heitmueller

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=4FAF4BBA.9090904@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alfredodelaiti@netscape.net \
    --cc=linux-media@vger.kernel.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.