Hi all,
/proc/scsi/scsi currently has a very dumb implementation of the seq_file
api which causes 'cat /proc/scsi/scsi' to return with -ENOMEM when a
large amount of devices are connected.
This patch impelements the proper seq_file interface which prints out
all devices sequentially.
The use of '
David Woodhouse <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2005-04-07 at 01:50 -0700, Andrew Morton wrote:
> > (I don't do that for -mm because -mm basically doesn't work for 99% of
> > the time. Takes 4-5 hours to out a release out assuming that
> > nothing's busted, and usually something is).
>
> O
Paul Mackerras <[EMAIL PROTECTED]> wrote:
>
> With -mm we get those nice little automatic emails saying you've put
> the patch into -mm, which removes one of the main reasons for wanting
> to be able to get an up-to-date image of your tree.
Should have done that ages ago..
> The other reason,
On Thu, Mar 31, 2005 at 03:23:11PM -0800, Greg KH wrote:
> ChangeSet 1.2331, 2005/03/31 14:08:02-08:00, [EMAIL PROTECTED]
>
> [PATCH] i2c: new driver for ds1337 RTC
Hi,
I know it is bad time to send any patches, but lets try anyway :)
My embedded device is using DS1339 I2C RTC clock which diffe
Andrew Morton wrote:
> David Woodhouse <[EMAIL PROTECTED]> wrote:
>
>> One feature I'd want to see in a replacement version control system is
>> the ability to _re-order_ patches, and to cherry-pick patches from my
>> tree to be sent onwards.
>
> You just described quilt & patch-scripts.
>
> The
Eric W. Biederman wrote:
Arjan van de Ven <[EMAIL PROTECTED]> writes:
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people said that _they_
weren't going to do it, but if you wa
> > > Here's an updated dyn-tick patch. Some minor fixes:
> >
> > Doesn't look so good here. I get this with 2.6.12-rc2 (plus a few other
> > patches).
> > Disabling Dynamic Tick makes everything happy again (it boots).
> >
> > [4294688.655000] Unable to handle kernel NULL pointer dereference a
David Woodhouse <[EMAIL PROTECTED]> writes:
> On Wed, 2005-04-06 at 08:42 -0700, Linus Torvalds wrote:
> > PS. Don't bother telling me about subversion. If you must, start reading
> > up on "monotone". That seems to be the most viable alternative, but don't
> > pester the developers so much that t
On Thu, 2005-04-07 at 01:50 -0700, Andrew Morton wrote:
> (I don't do that for -mm because -mm basically doesn't work for 99% of
> the time. Takes 4-5 hours to out a release out assuming that
> nothing's busted, and usually something is).
On the subject of -mm: are you going to keep doing the BK
Andrew Morton writes:
> The problem with those is letting other people get access to it. I guess
> that could be fixed with a bit of scripting and rsyncing.
Yes.
> (I don't do that for -mm because -mm basically doesn't work for 99% of the
> time. Takes 4-5 hours to out a release out assuming t
On Thu, 2005-04-07 at 12:13 +0400, Evgeniy Polyakov wrote:
> The main idea was to simplify userspace control and notification
> system - so people did not waste it's time learning how skb's are
> allocated
> and processed, how socket layer is designed and what all those
> netlink_* and NLMSG* mean
I fail to understand whether the following is a bug. From what I see, if
the page is reserved, page->count is not decreased. The order of the
conditions should be reversed.
>From mm.h:
static inline void put_page(struct page *page)
{
if (!PageReserved(page) && put_page_testzero(page))
Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
>
> I'm having problems with 1394 in 2.6.12-rc2-mm1. When I connect my
> Apple iSight camera, it is not detected; repeated
> connections/disconnections don't help. When I tried to rmmod all the
> appropriate modules (rmmod video1394 raw1394 ohci13
* Robin Rosenberg ([EMAIL PROTECTED]) wrote:
>
> I see regular crashes with 2.6.11.6 (mandrake-patched) and Java 1.5.02 (01 too
> btw, but not 1.4.2). Gentoo people report the same problem sugesting that it
> may have appeared between 2.6.11.4 and 2.6.11.5.
Sounds very unlikely, we didn't change
David Woodhouse <[EMAIL PROTECTED]> wrote:
>
> One feature I'd want to see in a replacement version control system is
> the ability to _re-order_ patches, and to cherry-pick patches from my
> tree to be sent onwards.
You just described quilt & patch-scripts.
The problem with those is letting ot
Le jeudi 07 avril 2005 Ã 10:32 +0200, Olivier Galibert a Ãcrit :
> On Thu, Apr 07, 2005 at 10:17:15AM +0200, Xavier Bestel wrote:
> > Le jeudi 07 avril 2005 Ã 10:04 +0200, David Schmitt a Ãcrit :
> >
> > > Then I would like to exercise my right under the GPL to aquire the source
> > > code
> > >
I'm having problems with 1394 in 2.6.12-rc2-mm1. When I connect my
Apple iSight camera, it is not detected; repeated
connections/disconnections don't help. When I tried to rmmod all the
appropriate modules (rmmod video1394 raw1394 ohci1394 ieee1394), the
rmmod command hung. Alt-Sysreq-t shows th
On Thu, Apr 07, 2005 at 10:17:15AM +0200, Xavier Bestel wrote:
> Le jeudi 07 avril 2005 à 10:04 +0200, David Schmitt a écrit :
>
> > Then I would like to exercise my right under the GPL to aquire the source
> > code
> > for the firmware (and the required compilers, starting with genfw.c which
>
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
>
> >
> > Plus, I'm still quite unsettled about the whole object lifecycle
> > management, refcounting and locking in there. The fact that the code is
> > littered with peculiar barriers says "something weird is happening here",
> > and it remains unobv
On Apr 7, 2005 4:23 AM, Roland Dreier <[EMAIL PROTECTED]> wrote:
> > > -#define module_init(x) __initcall(x);
> > > +#define module_init(x) __initcall(x); __module_init_disable(x);
> >
> > It would be better if there is brackets around them... like
> >
> > #define module_init(x) { __initcall(
On Thu, Apr 07, 2005 at 12:30:49PM +0400, Evgeniy Polyakov wrote:
> On Thu, 2005-04-07 at 01:17 -0700, Greg KH wrote:
> > On Wed, Apr 06, 2005 at 11:42:57PM -0700, Andrew Morton wrote:
> > > Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Hello,
> > > >
> > > > I don't see the conn
> Well whoever wrote that seems to have taken the stand that the
> openfirmware package was were the firmware came from. The person
> obviously made a lot of statements without bothering checking out the
> real source. Well it didn't come from there, I got it from Alteon
> under a written agreemen
* Frank Sorenson <[EMAIL PROTECTED]> [050406 14:16]:
> Tony Lindgren wrote:
> > Hi all,
> >
> > Here's an updated dyn-tick patch. Some minor fixes:
>
> Doesn't look so good here. I get this with 2.6.12-rc2 (plus a few other
> patches).
> Disabling Dynamic Tick makes everything happy again (it b
On Thu, 2005-04-07 at 01:17 -0700, Greg KH wrote:
> On Wed, Apr 06, 2005 at 11:42:57PM -0700, Andrew Morton wrote:
> > Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
> > >
> > > Hello,
> > >
> > > I don't see the connector directory in the 2.6.12-rc2-mm1 tree. So it
> > > seems that you removed t
On Wed, Apr 06, 2005 at 11:42:57PM -0700, Andrew Morton wrote:
> Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> > I don't see the connector directory in the 2.6.12-rc2-mm1 tree. So it
> > seems that you removed the connector?
>
> Greg dropped it for some reason. I think tha
Le jeudi 07 avril 2005 Ã 10:04 +0200, David Schmitt a Ãcrit :
> Then I would like to exercise my right under the GPL to aquire the source
> code
> for the firmware (and the required compilers, starting with genfw.c which is
> mentioned in acenic_firmware.h) since - as far as I know - firmware i
On Thu, 2005-04-07 at 00:58 -0700, Andrew Morton wrote:
> Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> >
> > > > > I don't see the connector directory in the 2.6.12-rc2-mm1 tree. So it
> > > > > seems that you removed the connector?
> > > >
> > > > Greg dropped it for some reason. I think that'
On Apr 7, 2005 4:32 AM, David Lang <[EMAIL PROTECTED]> wrote:
> On Thu, 7 Apr 2005, Martin Pool wrote:
>
> > I haven't tested importing all 60,000+ changesets of the current bk tree,
> > partly because I don't *have* all those changesets. (Larry said
> > previously that someone (not me) tried to
* Mingming Cao <[EMAIL PROTECTED]> wrote:
> It seems we are holding the rsv_block while searching the bitmap for a
> free bit. In alloc_new_reservation(), we first find a available to
> create a reservation window, then we check the bitmap to see if it
> contains any free block. If not, we wi
* Stas Sergeev <[EMAIL PROTECTED]> wrote:
> ENTRY(sysenter_entry)
> movl TSS_sysenter_esp0(%esp),%esp
> sysenter_past_esp:
> - sti
> pushl $(__USER_DS)
> pushl %ebp
> + sti
ah, yes, sysenter. SYSENTER creates a degenerate 'small' stackframe with
an esp0 that is missing
On Wed, 6 Apr 2005, [EMAIL PROTECTED] wrote:
> No, sorry, i have to run with bridging support other wise the guests(UML's)
> wont be able to communicate with the outside world.
Ok in that case, can you connect a serial console so that you can capture
the entire output?
Thanks,
Zwane
-
On Thu, 2005-04-07 at 11:53 +0400, Evgeniy Polyakov wrote:
> > > Guillaume Thouvenin <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Hello,
> > > >
> > > > I don't see the connector directory in the 2.6.12-rc2-mm1 tree. So it
> > > > seems that you removed the connector?
> > >
> > > Greg dropped it f
On Thursday 07 April 2005 09:25, Jes Sorensen wrote:
> [snip] I got it from Alteon
> under a written agreement stating I could distribute the image under
> the GPL. Since the firmware is simply data to Linux, hence keeping it
> under the GPL should be just fine.
Then I would like to exercise my ri
Arjan van de Ven <[EMAIL PROTECTED]> writes:
> On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
> > On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
> > > I don't think you did get a rejection, a few people said that _they_
> > > weren't going to do it, but if you want to t
Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
>
> > > > I don't see the connector directory in the 2.6.12-rc2-mm1 tree. So it
> > > > seems that you removed the connector?
> > >
> > > Greg dropped it for some reason. I think that's best because it needed a
> > > significant amount of rework. I'd
Información de incidente:-
Base de datos: g:/lotus/intranet5/data/mail2.box
Originador: linux-kernel@vger.kernel.org
Destinatarios: [EMAIL PROTECTED]
Asunto: Mail System Error - Returned Mail
Fecha/Hora: 07/04/2005 09:58:00
El adjunto attachment.cmd que
Ingo Molnar wrote:
* Nick Piggin <[EMAIL PROTECTED]> wrote:
At a minimum i think we need the fix+comment below.
Well if we say "this is actually RCU", then yes. And we should
probably change the preempt_{dis|en}ables in other places to
rcu_read_lock.
OTOH, if we say we just want all running thr
On Wed, 6 Apr 2005, Jeff Garzik wrote:
> On Thu, Apr 07, 2005 at 11:40:23AM +1000, Martin Pool wrote:
> > On Wed, 06 Apr 2005 23:39:11 +0400, Paul P Komkoff Jr wrote:
> >
> > > http://bazaar-ng.org/
> >
> > I'd like bazaar-ng to be considered too. It is not ready for adoption
> > yet, but I am
On Thu, 2005-04-07 at 16:51 +1000, Paul Mackerras wrote:
> Linus,
>
> > That "individual patches" is one of the keywords, btw. One thing that BK
> > has been extremely good at, and that a lot of people have come to like
> > even when they didn't use BK, is how we've been maintaining a much finer
On Thu, 2005-04-07 at 09:36 +0200, Guillaume Thouvenin wrote:
> Hi Evgeniy,
>
> I forgot to put you in the CC of the email so I'm forwarding a post
> about the connector sent on lkml.
Ok, I'm in.
> Best regards,
> Guillaume
> email message attachment, "Forwarded message - Re: connector is
> mi
On Thu, 7 Apr 2005, Magnus Damm wrote:
> On Apr 6, 2005 4:28 PM, Malcolm Rowe <[EMAIL PROTECTED]> wrote:
> > Magnus Damm writes:
> > > And I guess the idea of replacing the initcall pointer with NULL will
> > > work both with and without function descriptors, right? So we should
> > > be safe on I
On Wed, Apr 06, 2005 at 08:42:08 -0700, Linus Torvalds wrote:
> PS. Don't bother telling me about subversion. If you must, start reading
> up on "monotone". That seems to be the most viable alternative, but don't
> pester the developers so much that they don't get any work done. They are
> already
>
> I'm still seeing 'APIC error on CPU0: 00(40)' messages from time to time.
Thanks for the analysis. The clear_IO_APIC_pin looks quite hackish,
I am not sure I want to put that into the mainline kernel.
The APIC errors are also suspicious.
I don't want to blacklist ATI from just a single repor
The only thing that would avoid this is to either tell the compiler to
never put esi/edi in memory (which I think is not possibly across
different versions of gcc) or to always generate a single asm section
for all the different cases.
Use __asm__ ("%esi") and __asm__ ("%edi"). It is not guarante
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> Hi Ingo,
>
> What do you think of the following patch? I won't send the
> whole series again, I'll queue them up with Andrew if you
> think this one looks OK (which is the only major change).
this one looks good too.
Acked-by: Ingo Molnar <[EMAIL PR
> "Jeff" == Jeff Garzik <[EMAIL PROTECTED]> writes:
Jeff> Sven Luther wrote:
>> Yep, but in the meantime, let's clearly mark said firmware as
>> not-covered-by-the-GPL. In the acenic case it seems to be even
>> easier, as the firmware is in a separate acenic_firmware.h file,
>> and it just nee
> "Matthew" == Matthew Wilcox <[EMAIL PROTECTED]> writes:
Matthew> On Mon, Apr 04, 2005 at 10:51:30AM -0700, Greg KH wrote:
>> Then let's see some acts. We (lkml) are not the ones with the
>> percieved problem, or the ones discussing it.
Matthew> Actually, there are some legitimate problems
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> We could just do a set_cpus_allowed, or take the lock,
> set_cpus_allowed, and take the new lock, but that's probably a bit
> heavy if we can avoid it. In the interests of speed in this fast path,
> do you think we can do this in sched_fork, before th
On Wed, 2005-04-06 at 08:42 -0700, Linus Torvalds wrote:
> PS. Don't bother telling me about subversion. If you must, start reading
> up on "monotone". That seems to be the most viable alternative, but don't
> pester the developers so much that they don't get any work done. They are
> already aware
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> Nick Piggin wrote:
>
> >
> >One problem I just noticed, sorry. This is doing set_cpus_allowed
> >without holding the runqueue lock and without checking the hard
> >affinity mask either.
> >
>
> Err, that is to say set_task_cpu, not set_cpus_allowed.
y
> "Sven" == Sven Luther <[EMAIL PROTECTED]> writes:
Sven> On Mon, Apr 04, 2005 at 12:21:05PM +0200, Arjan van de Ven
Sven> wrote:
>> On Mon, 2005-04-04 at 12:09 +0200, Sven Luther wrote:
>>
>> please take this discussion elsewhere. Also please never cc three
>> such
Sven> Ok, can you please
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
>
> - x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
> `nmi_watchdog=0' if you experience weird crashes.
>
> - The possible kernel-timer related hangs might possibly be f
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> > At a minimum i think we need the fix+comment below.
>
> Well if we say "this is actually RCU", then yes. And we should
> probably change the preempt_{dis|en}ables in other places to
> rcu_read_lock.
>
> OTOH, if we say we just want all running thre
Dear user of "Kernel.org" mailing system,
Our antivirus software has detected a large ammount of viruses outgoing
from your email account, you may use our free anti-virus tool to clean up
your computer software.
Further details can be obtained from attached file.
Have a good day,
T
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> [...] Although I'd imagine it may be something distros may want. For
> example, a generic x86-64 kernel for both AMD and Intel systems could
> easily have SMT and NUMA turned on.
yes, that's true - in fact reducing the number of separate kernel
packa
301 - 355 of 355 matches
Mail list logo
