From: "J.A. Magallon" <jamagallon@able.es>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Patch series to remove devfs [00/22]
Date: Mon, 13 Jun 2005 19:51:53 +0000 [thread overview]
Message-ID: <1118692313l.5759l.0l@werewolf.able.es> (raw)
In-Reply-To: <20050613174355.GB12517@suse.de> (from gregkh@suse.de on Mon Jun 13 19:43:55 2005)
On 06.13, Greg KH wrote:
> On Sun, Jun 12, 2005 at 10:44:33PM +0000, J.A. Magallon wrote:
> >
> > On 06.11, Greg KH wrote:
> > > As everyone knows[1], devfs is going to be removed from the kernel soon.
> > > To accomplish this, here is a series of patches (22 in all) that do just
> > > that. Surprisingly enough, devfs was almost everywhere in the kernel,
> > > that's why it takes so many patches :)
> > >
> >
> > You missed this for -mm, do not know if they apply to mainline:
>
> This patch series was not for -mm, as my comments stated :)
>
I shifted some offsets and am running it now...
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.0 (Cooker) for i586
Linux 2.6.11-jam25 (gcc 4.0.0 (4.0.0-3mdk for Mandriva Linux release 2006.0))
prev parent reply other threads:[~2005-06-13 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 7:43 Greg KH
2005-06-11 10:21 ` Adrian Bunk
2005-06-11 14:39 ` Greg KH
2005-06-11 15:36 ` Adrian Bunk
2005-06-11 15:41 ` Christoph Hellwig
2005-06-11 15:59 ` Adrian Bunk
2005-06-11 15:44 ` Kay Sievers
2005-06-11 20:14 ` [2.6 patch] fix compile errors and warning after devfs removal patches Adrian Bunk
2005-06-16 21:34 ` Greg KH
2005-06-12 22:44 ` [RFC] Patch series to remove devfs [00/22] J.A. Magallon
2005-06-13 17:43 ` Greg KH
2005-06-13 19:51 ` J.A. Magallon [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=1118692313l.5759l.0l@werewolf.able.es \
--to=jamagallon@able.es \
--cc=gregkh@suse.de \
--cc=linux-kernel@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 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®