Hi, I am Ryan. I consider myself an easy-going man,honest and loving person. I
am currently looking for a relationship in which i feel loved.
Please tell me more about yourself, if you do not mind.
Regards,
Ryan Ellis.
> Okay, thanks. In the meantime, is it possible for you to lock the
> man-pages component so that no further bug reports can be made via
> that component?
It's not just the man-pages component. I'm seeing the same spam starting
up on backports.
>> W: http://linuxwimax.org
That URL doesn't work. There's no address associated with the domain.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.htm
Best,
J.
On Nov 21, 2012, at 4:37 PM, Jan Kara wrote:
> On Wed 21-11-12 13:29:01, Christoph Hellwig wrote:
>> On Wed, Nov 21, 2012 at 11:58:05AM -0500, Jeff Moyer wrote:
I'd like to use this as a vehicle to revisit how dio completions work.
>>>
>>> I don't like the sound of that. ;-)
On 19/11/12 02:30, Arend van Spriel wrote:
On 11/18/2012 11:47 AM, Mark Ellis wrote:
1. rfkill code removal causes hang
2. the rfkill code was removed from this driver in commit
53039f222c548bfc119eea6df4dca2b57550e271 this results in my computer
hanging (dell n5050) if booting with the
1. rfkill code removal causes hang
2. the rfkill code was removed from this driver in commit
53039f222c548bfc119eea6df4dca2b57550e271 this results in my computer
hanging (dell n5050) if booting with the wireless (hardware) disabled.
downgrading this module to the version prior to this commit f
On 15 Feb 2008, at 21:45, Benjamin Herrenschmidt wrote:
On Fri, 2008-02-15 at 15:53 +, Alan Cox wrote:
That's strange though. Somebody with knowledge of that HW (or
specs) who
can spot something ? Could it be an issue with timing ?
I don't have HW access to this machine. If somebody co
Hi,
This change causes attached drives to no longer be detected and
function on the PowerPC Buffalo Linkstation machines:
<7>pata_sil680 :00:0c.0: version 0.4.8
<6>sil680: 133MHz clock.
<6>scsi0 : pata_sil680
<6>scsi1 : pata_sil680
<6>ata1: PATA max UDMA/133 irq 18
<6>ata2: PATA max UDMA/1
linux-os (Dick Johnson) wrote:
I seem to be running into a limit of 64 queued datagrams. This isn't a
data buffer size; varying the size of the datagram makes no difference
in the observed queue size. If more datagrams are sent before some are
read, they are silently dropped. (By "silently," I
(Posted a few days ago to c.os.l.networking; no replies there.)
I seem to be running into a limit of 64 queued datagrams. This isn't a
data buffer size; varying the size of the datagram makes no difference
in the observed queue size. If more datagrams are sent before some are
read, they are sil
Cross compiling kernel (any recent version) on any non-64bit host (ie:
x86) to
ALPHA the "make bootpfile" step fails. The problem is localized
to arch/alpha/boot/tools/objstrip.c
Various 'elf' structure members are 64 bit, not 32bit and the wrong
version of
the structure is being choosen. (To b
On Fri, 24 Nov 2000 12:28:44 Andrew Morton wrote:
> Mark Ellis wrote:
> >
> > Hi all, consistently getting the following when pppd is terminated.
>
> When pppd downs the ppp0 device, unregister_netdevice() is
> trying to run /sbin/hotplug in a new kernel thread. That
>
Hi all, consistently getting the following when pppd is terminated. Happens
in 2.4.0-test11, fine in 2.4.0-test9, don't know about test10. Same happens
for pppd 2.4.0b4 and 2.4.0, both recompiled for test11. Is this related to
the modutils incompatability (modutils 2.3.19) ?
CONFIG_PPP and CONFI
13 matches
Mail list logo
