public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: CityK <cityk@rogers.com>
To: "Miroslav Šustek" <sustmidown@centrum.cz>
Cc: linux-media@vger.kernel.org, mchehab@infradead.org
Subject: Re: [PATCH] Leadtek WinFast DTV-1800H support
Date: Sun, 31 May 2009 14:04:01 -0400	[thread overview]
Message-ID: <4A22C691.1000100@rogers.com> (raw)
In-Reply-To: <200905291632.28450@centrum.cz>

Miroslav Šustek wrote:
> Any problem with this patch?
> I'm trying to get WinFast DTV-1800H support into repository for seven months.
> (see:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/1125/match=1800h
>
>   

Hi Miro,

Its unfortunate that the patch hasn't been added yet, but I do see a
problem (in its current form) that explains why it hasn't been picked
up.   For the sake of thoroughness, here's an audit trail of the entire
history:

1) http://linuxtv.org/pipermail/linux-dvb/2008-October/029859.html
- Steve picked up some style flaws
- (Although it is more desirable to include patches inline as opposed to
as attachments, I note that the attached patch is of type
"text/x-patch", which is fine)

2) http://linuxtv.org/pipermail/linux-dvb/2008-November/030362.html
- I noticed your missing SOB
- (Again, I note that the attached patch is of type "text/x-patch",
which is fine)

3)
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/1125/match=1800h
- You note in your message that your prior patch didn't get picked up
possibly because of the switch of mail lists.  That is quite possible,
but whatever the case, your patch was, indeed, lost.
- Herman responded with some suggestions, as well as noting that your
SOB was absent again with the attached patches (though, I know you had
resubmitted back in Nov with a SOB)
- But here starts the most recent problem: unfortunately, the attached
patches where of type "application/octet-stream", which the patchwork
tool will NOT pick up.  Please see:
http://www.linuxtv.org/wiki/index.php/Development:_How_to_submit_patches
This is a summary explanation of the submitting process (which includes
links to several of the documents you've undoubtedly already read) and
touches upon attachments.

4) http://www.mail-archive.com/linux-media@vger.kernel.org/msg05856.html
-  in Hermann's follow up, he correctly notes that the patches never
made it onto the patchwork queue (see my explanation directly above for
why they were not).

5) http://www.mail-archive.com/linux-media@vger.kernel.org/msg05888.html
> Nobody noticed the previous post(s).
>   
- Ha, I beg to differ! -- at the very least, Steve, myself and Hermann
have all spotted your prior patches and have commented.
- Unfortunately, the attached patch is again of the type
"application/octet-stream" and will NOT be automatically picked up by
patchwork


6) http://www.mail-archive.com/linux-media@vger.kernel.org/msg05890.html
> (Shoot me! Now it's correct.)
>   
- Nope.  The attached patch is still a type "application/octet-stream",
and that is why it is not showing up on the patchwork queue list
- I have also just noticed that Trent has also now commented on the
patches (so add another to the list!)

/End of audit trail

I understand your frustration and I don't mean to be bureaucratic (I
have zero say in what patches get picked up), but I hope I have shed
some light upon what has gone wrong over the last several months. 
Although I'd rather suspect that Mauro is now well aware of the issue,
I'd urge you to resubmit (following the recommendations from the link I
provided above) so that it gets picked up and placed upon the patchwork
list.





  reply	other threads:[~2009-05-31 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200905291628.32305@centrum.cz>
     [not found] ` <200905291629.364@centrum.cz>
     [not found]   ` <200905291630.21607@centrum.cz>
     [not found]     ` <200905291631.1309@centrum.cz>
     [not found]       ` <200905291632.13608@centrum.cz>
2009-05-29 14:32         ` [PATCH] Leadtek WinFast DTV-1800H support Miroslav  Šustek
2009-05-31 18:04           ` CityK [this message]
     [not found] <200905311925.19140@centrum.cz>
     [not found] ` <200905311926.3696@centrum.cz>
     [not found]   ` <200905311927.20442@centrum.cz>
     [not found]     ` <200905311928.4713@centrum.cz>
     [not found]       ` <200905311929.21561@centrum.cz>
     [not found]         ` <200905311930.5668@centrum.cz>
     [not found]           ` <200905311931.18645@centrum.cz>
     [not found]             ` <200905311932.22284@centrum.cz>
     [not found]               ` <200905311933.22524@centrum.cz>
2009-05-31 20:50                 ` Trent Piepho
     [not found] <200905291638.9584@centrum.cz>
2009-05-29 14:39 ` Miroslav  Šustek
2009-05-31 13:34   ` Trent Piepho
2009-05-31 17:39     ` Miroslav  Šustek
2009-05-31 19:58       ` Mauro Carvalho Chehab
2009-06-01  1:58         ` hermann pitton
2009-06-01  9:07           ` Mauro Carvalho Chehab
2009-06-01 22:26             ` hermann pitton
2009-05-31 19:28     ` Miroslav Šustek
     [not found] <200905102337.22307@centrum.cz>
     [not found] ` <200905102338.14151@centrum.cz>
     [not found]   ` <200905102339.24789@centrum.cz>
2009-05-10 21:39     ` Miroslav  Šustek
2009-05-28 18:44       ` Miroslav Šustek
2009-05-28 19:42         ` hermann pitton

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=4A22C691.1000100@rogers.com \
    --to=cityk@rogers.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=sustmidown@centrum.cz \
    /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