All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Takashi Iwai <tiwai@suse.de>,
	linux-next@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: CONFIG_KMOD breakage in next kernel
Date: Mon, 25 Aug 2008 10:13:58 +1000	[thread overview]
Message-ID: <200808251013.58975.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1219256165.3502.10.camel@johannes.berg>

On Thursday 21 August 2008 04:16:05 Johannes Berg wrote:
> Hi,
>
> > I found that CONFIG_KMOD was already removed in linux-next tree.
> > This seems to result in many breakages.  For example, I cannot mount a
> > FAT device automatically because of failure of automatic loading of
> > nls modules.
>
> This is odd. I had posted a long series of patches removing all of the
> users I had found (similar grep like the one you used), see
> http://lkml.org/lkml/2008/7/9/150 for the whole thread.
>
>
> For some reason, only seven of those eleven patches ended up in the
> kernel, you had taken the alsa one and Rusty posted only six of them.

OK, not quite sure what happened.  I'll grab the rest and push them into 
tomorrow's linux-next.

For today, I'll pull out the CONFIG_KMOD removal.

Thanks,
Rusty.

  reply	other threads:[~2008-08-25  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 16:16 CONFIG_KMOD breakage in next kernel Takashi Iwai
2008-08-20 17:16 ` Marcel Holtmann
2008-08-20 18:44   ` Johannes Berg
2008-08-21  1:49     ` Marcel Holtmann
2008-08-20 18:16 ` Johannes Berg
2008-08-25  0:13   ` Rusty Russell [this message]
2008-08-25  0:28     ` Stephen Rothwell

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=200808251013.58975.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    --cc=video4linux-list@redhat.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.