linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <glikely@gmail.com>
To: Mark Chambers <markc@mail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC52xx: sysfs failure on adding new device driver
Date: Thu, 9 Jun 2005 12:34:39 -0600	[thread overview]
Message-ID: <528646bc05060911346487aaf4@mail.gmail.com> (raw)
In-Reply-To: <00b701c56d07$e3b166a0$0301a8c0@chuck2>

On 6/9/05, Mark Chambers <markc@mail.com> wrote:
> Sylvain:
> > btw, if not yet integrated you should send your patch to Wolfang, he's
> > the one maintaining that tree.
>=20
> Wolfgang:
> > I've seen the patch, but did not decide yet what to do with it.  Many
> > drivers  don't  support  devfs  anyway, and in my opinion devfs makes
> > little sense in embedded systems anyway. Not to mention that it  will
> > officially  be removed from the kernel tree in less than 4 weeks from
> > now (see Documentation/feature-removal-schedule.txt).
>=20
> This is nonsense.  You know, when I made this patch I said
> to myself, "Self, you're wasting your time, these guys won't take patches
> from somebody they don't know"  But I thought it was enough of a
> no-brainer that it might go through.
>=20
> Seems I was wrong.
>=20
Don't take things too personally.  (I understand where you're coming
from; I'm virtually unknown around here also).  You have to remember
that devfs is pretty much considered to be a bastard stepchild and
there is a lot of negative opinion surrounding it.  Because of that it
is very hard to get *any* devfs patches to be considered.

Just posting your patch on the ML is important and valuable.  That
makes things easy when somebody else has the same problem.  I
certainly remember seeing your original post, and I made note of it
for if I ever see that problem.

Cheers,
g.

  reply	other threads:[~2005-06-09 18:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 23:51 MPC52xx: sysfs failure on adding new device driver Grant Likely
2005-06-09 11:21 ` Mark Chambers
2005-06-09 11:32   ` Sylvain Munaut
2005-06-09 13:55     ` Wolfgang Denk
2005-06-09 15:28       ` Mark Chambers
2005-06-09 18:34         ` Grant Likely [this message]
2005-06-09 11:28 ` Sylvain Munaut
2005-06-09 14:54   ` Grant Likely
2005-06-09 15:20     ` Kumar Gala
2005-06-09 18:48       ` Grant Likely
2005-06-10 14:09         ` Sylvain Munaut
2005-06-10 16:06           ` Grant Likely
2005-06-13 19:08           ` Grant Likely

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=528646bc05060911346487aaf4@mail.gmail.com \
    --to=glikely@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=markc@mail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).