From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Michael Krufky <mkrufky@kernellabs.com>
Cc: linux-media <linux-media@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PULL] http://kernellabs.com/hg/~mkrufky/sms1xxx
Date: Tue, 1 Sep 2009 16:36:04 -0300 [thread overview]
Message-ID: <20090901163604.04599211@pedra.chehab.org> (raw)
In-Reply-To: <303a8ee30909010803r69f18fa0n8d40f164cf51607f@mail.gmail.com>
Em Tue, 1 Sep 2009 11:03:14 -0400
Michael Krufky <mkrufky@kernellabs.com> escreveu:
> The Kconfig symbol names were changed, the target object has changed,
> the module filename has changed.
>
> A submenu was added, the USB support is not enabled by default.
>
> None of the above fixed any bug, it just makes unnecessary changes
> that are inappropriate this late in a kernel development cycle.
None of the above breaks anything, and enabling a driver by default is not good
anyway.
> If a bug needed to be fixed, it would have been as simple as adding
> the new object file for smssdio.o , and the old
> DVB_SIANO_SMS1XXX_SMS_IDS section could have been removed without
> changing everything.
>
> I think this is ridiculous to slip in at the last moment, but I would
> have had no complaints seeing this in the next merge window.
>
> What is the point of a "merge window" if you let people make such
> changes as this right before a kernel is released.
The patch is a bug fix and it is even older than your LED fix. The first
version were submitted before the previous merge window, and you asked for some
changes that were done accordingly.
Since the entire Siano driver suffered major changes at the last merge window,
this patch needs to be available together with the remaining series of the
Siano series of patches, to reflect the changes that happened inside the
driver, and the inclusion of the SDIO driver.
Cheers,
Mauro
prev parent reply other threads:[~2009-09-01 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090730200714.5a7ab8a6@pedra.chehab.org>
[not found] ` <37219a840907310825n51d5a6bar79ea1f31dd889327@mail.gmail.com>
[not found] ` <20090801014053.7f53da83@pedra.chehab.org>
[not found] ` <303a8ee30908011103n3c12258icd2bfd1305b419d3@mail.gmail.com>
[not found] ` <20090811140128.211d4d11@caramujo.chehab.org>
[not found] ` <37219a840908111457o4b6abc64n52291f044b56782d@mail.gmail.com>
[not found] ` <37219a840908241332w2e2d45d8kd6406de3e60d1317@mail.gmail.com>
2009-08-30 12:53 ` [PULL] http://kernellabs.com/hg/~mkrufky/sms1xxx Michael Krufky
2009-08-30 22:13 ` Mauro Carvalho Chehab
2009-08-31 11:03 ` Michael Krufky
2009-09-01 13:47 ` Mauro Carvalho Chehab
2009-09-01 15:03 ` Michael Krufky
2009-09-01 19:36 ` 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=20090901163604.04599211@pedra.chehab.org \
--to=mchehab@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mkrufky@kernellabs.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.