mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Jean Delvare <khali@linux-fr.org>,
	"D. Kelly" <user.kernel@gmail.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	"mailing list: linux-kernel" <linux-kernel@vger.kernel.org>,
	Linux I2C <i2c@lm-sensors.org>
Subject: Re: Problem with restricted I2C algorithms in kernel 2.6.26!
Date: Sun, 10 Aug 2008 14:07:05 +0300	[thread overview]
Message-ID: <20080810110705.GD16146@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <Pine.LNX.4.58.0808081037080.3151@shell2.speakeasy.net>

On Fri, Aug 08, 2008 at 10:52:05AM -0700, Trent Piepho wrote:
> On Fri, 8 Aug 2008, Jean Delvare wrote:
> > On Thu, 7 Aug 2008 16:41:10 -0700 (PDT), Trent Piepho wrote:
> > > Expecting every developer to keep abreast of linux-next and the tens of
> > > thousands of patches it gets just isn't realisitic.
> > >
> > > The embedded platforms I develop on won't run linux-next.  Continuously
> > > porting them to linux-next is simply impossible.  The man hours required to
> > > do that would be staggering.
> >
> > Once again a "believe me it's impossible" without any good reason
> > given. I fail to see why embedded platforms would be any different from
> > other platforms or subsystem trees. Please enlighten me.
> 
> Because they usually require lots of additional patches that aren't in the
> kernel.  Sometimes embedded developers try to get these patches into the
> mainline kernel, but some maintainers aren't interested in accepting
> patches that don't appear to be useful to desktop users.
>...

The last thing mustn't happen.

Can you give examples?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-08-10 11:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 19:33 D. Kelly
2008-07-26  6:59 ` Andrew Morton
2008-07-26 14:34   ` [i2c] " Jon Smirl
2008-08-07 11:13 ` Jean Delvare
2008-08-07 16:01   ` [i2c] " Trent Piepho
2008-08-07 16:14     ` Jean Delvare
2008-08-07 17:19       ` Jean Delvare
2008-08-07 17:29         ` Randy Dunlap
2008-08-07 23:41       ` Trent Piepho
2008-08-08  9:37         ` Jean Delvare
2008-08-08 17:52           ` Trent Piepho
2008-08-10 11:07             ` Adrian Bunk [this message]
2008-08-07 18:39   ` Sam Ravnborg
2008-08-07 18:49     ` Jean Delvare
2008-08-07 19:03       ` Michael Krufky
2008-08-07 21:06         ` Jean Delvare
2008-08-07 21:34 mkrufky
2008-08-08  0:17 ` Stefan Richter
2008-08-08  9:28 ` Jean Delvare

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=20080810110705.GD16146@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=i2c@lm-sensors.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=user.kernel@gmail.com \
    --cc=xyzzy@speakeasy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®