On Thu, Feb 21, 2008 at 10:29:09PM -0800, Junio C Hamano wrote:
Linus Torvalds [EMAIL PROTECTED] writes:
So I'd be happier with warnings about deep indentation (but how do you
count it? Will people then try to fake things out by using 4-space indents
and then deep indentations will look
On 2/22/08 12:09 AM, Roland Dreier [EMAIL PROTECTED] wrote:
I think we can assume that the ringing of the doorbell is synchronous,
i.e. when the processor completes it's write, the card knows there are
RQ WQE available in host memory,
It doesn't affect your larger point, but to be
Get original and perfectly functioning software at low prices. All software
can be downloaded immediately after purchase. Impressive selection of programs
even for Macintosh! Programs in many languages are available.
We provide help in installing software. You can ask any question and get a
On Fri, 22 Feb 2008 01:05:26 +0100
Krzysztof Halasa [EMAIL PROTECTED] wrote:
Jeff Garzik [EMAIL PROTECTED] writes:
If a driver is full of lines of length 80, that's a problem.
I'm not sure.
We all have more than 80-chars wide displays for years, don't we? The
Even a vt132 serial
Hello with love,
I am ruth tall slim that love sightseeing, i was going over the computer
today and came across your email and got interested in knowing more about
you for important discussion reply to me via my mail address if you care (
[EMAIL PROTECTED]) i will send my pics later.
Thanks,
This email was generated automatically, please do not reply
git_url: git://git.openfabrics.org/ofed_1_3/linux-2.6.git
git_branch: ofed_kernel
Common build parameters: --with-ipoib-mod --with-sdp-mod --with-srp-mod
--with-user_mad-mod --with-user_access-mod --with-mthca-mod --with-mlx4-mod
On Fri, Feb 22, 2008 at 2:46 AM, David Newall [EMAIL PROTECTED] wrote:
Krzysztof Halasa wrote:
Perhaps we should increase line length limit, 132 should be fine.
Especially useful with long printk() lines and long arithmetic
expressions.
Yes; or even longer. 80 characters might have
Bart Van Assche wrote:
There is a reason to limit line length: scientific research has shown
that readability of regular texts is optimal for a line length between
55 and 65 characters.
Putting aside the point that we're talking code, not regular text, I've
heard that said before and I don't
Hi Tim,
On Thu, 2008-02-21 at 16:27 -0800, Timothy A. Meier wrote:
LLNL uses the remote console feature in OpenSM. We have a need to secure
this remote connection with authentication/authorization and encryption
(specifically PAM and OpenSSL). I have a working prototype, and would
like to
Hello! I am bored today. I am nice girl that would like to chat with you. Email
me at [EMAIL PROTECTED] only, because I am using my friend's email to write
this. Will send some of my pictures
___
general mailing list
general@lists.openfabrics.org
On Sat, 2008-02-23 at 00:55 +1030, David Newall wrote:
Bart Van Assche wrote:
There is a reason to limit line length: scientific research has shown
that readability of regular texts is optimal for a line length between
55 and 65 characters.
Putting aside the point that we're talking
Don't waste time waiting for delivery of your software on a CD. Download and
install it immediately. Choose the program you need from more than 270 programs
in many languages.
We are glad to help you to install your software. Feel free to ask questions
and receive highly professional
On Sat, Feb 23, 2008 at 12:55:03AM +1030, David Newall wrote:
Bart Van Assche wrote:
There is a reason to limit line length: scientific research has shown
that readability of regular texts is optimal for a line length between
55 and 65 characters.
Putting aside the point that we're
When I worked on OFED-1.3-rc2, I happened to notice that even
though ib_rcp.c includes the scsi_transport_srp.h header and called into the
functions in scsi_transport_srp.c such as srp_remove_host,
however, scsi_transport_srp.ko has never been loaded in my system. However
it seems to be working
Tom Tucker wrote:
Ok. So what does the HW do with the packet while it's pondering it's
options? It has to put it somewhere.
At the point where the RQ/SRQ would be checked the HW should not have
to put the packet anywhere. At least not until it can allocate a WQE
or declare a
On Thu, 2008-02-21 at 22:15 -0800, Shirley Ma wrote:
Hello Ralph,
ib_ipoib uses shared receive queues and doesn't try to manage
posted buffer credits so the RNR NAK issue isn't the same
as what Steve is trying to do.
I meant the problem you saw might be the same reason. How many
Use CL_HTON64() macro for constant conversion instead of cl_ntoh64()
function. Also it changes conversion direction since this value used in
network byte order.
Signed-off-by: Sasha Khapyorsky [EMAIL PROTECTED]
---
opensm/libvendor/osm_vendor_ibumad.c |2 +-
1 files changed, 1
When a cm mad is received, it is queued to a cm workqueue for
processing. The queued work item references the port and device
on which the mad was received. If that device is removed from
the system before the work item can execute, the work item will
reference freed memory.
To fix this, flush
* Linus Torvalds [EMAIL PROTECTED] wrote:
I'm personally of the opinion that a lot of checkpatch fixes are
anything but. That mainly concerns fixing overlong lines (where the
fixed version is usually worse than the original), but it's been
true for some other warnings too.
that was
On Fri, Feb 22, 2008 at 04:17:17PM +0100, Peter Zijlstra wrote:
Even with e-mail, I can easily show over 200 characters wide with a
large font (say 11pt) but find it harder to read emails that don't
nicely wrap at 78. So much so that I often find myself not reading the
mail, or restyling it
In put_madw() pass transaction id by value as it used there and not by
refernce.
Signed-off-by: Sasha Khapyorsky [EMAIL PROTECTED]
---
opensm/libvendor/osm_vendor_ibumad.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/opensm/libvendor/osm_vendor_ibumad.c
On Fri, Feb 22, 2008 at 7:54 PM, Ingo Molnar [EMAIL PROTECTED] wrote:
If a patch or if a file has a clean _style_, bugs and deeper
structural problems often stand out like a sore thumb. But if the
code is peppered with random style noise, it's a lot harder (for me
at least) to
Ingo Molnar wrote:
2) you might know that Deja-Vu moment when you look at a new patch that
has been submitted to lkml and you have a strange, weird feeling
that there's something wrong about the patch.
It's totally subconscious, and you take a closer look and a few
seconds
On Fri, Feb 22, 2008 at 02:20:12PM -0500, Jeff Garzik wrote:
Ingo Molnar wrote:
2) you might know that Deja-Vu moment when you look at a new patch that
has been submitted to lkml and you have a strange, weird feeling
that there's something wrong about the patch.
It's totally
On Thu 2008-02-21 14:08:55, Arjan van de Ven wrote:
On Thu, 21 Feb 2008 23:01:24 +0200
Adrian Bunk [EMAIL PROTECTED] wrote:
[ Linus Added to the To: since I want to hear his opinion on this
issue. ]
On Thu, Feb 21, 2008 at 12:28:55PM -0800, Roland Dreier wrote:
This driver should
On Fri 2008-02-22 01:05:26, Krzysztof Halasa wrote:
Jeff Garzik [EMAIL PROTECTED] writes:
If a driver is full of lines of length 80, that's a problem.
I'm not sure.
We all have more than 80-chars wide displays for years, don't we? The
No.
Zaurus is one example, second is small screen
___
general mailing list
general@lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
Linus Torvalds [EMAIL PROTECTED] writes:
Will people then try to fake things out by using 4-space indents
and then deep indentations will look like just a couple of tabs?)
There is no point in faking it as it's only advisory, it's to help the
author who should be free to ignore the advice.
Pavel Machek [EMAIL PROTECTED] writes:
Zaurus is one example, second is small screen where you need big font
to keep it readable (x60 on desk).
Come on, are you doing Linux kernel development on PDA?
--
Krzysztof Halasa
___
general mailing list
Peter Zijlstra [EMAIL PROTECTED] writes:
So, yes, I have the screen estate for very long lines, but I find that
long lines require more effort to read (that very much includes leading
whitespace). Also, since long lines are rare (and they should be, if you
nest too deep you have other issues)
On Fri, Feb 22, 2008 at 11:59:35PM +0100, Krzysztof Halasa wrote:
Sure - because email is not C code.
Actually you don't read C code, word by word, as you read books - do
you?
If it's decently written - sure, why not? Unfortunately, more common case
is somewhere between the writing on the
ForValuedCustomerSpecialPricesCertified
http://joycearcostu.blogspot.com
___
general mailing list
general@lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit
32 matches
Mail list logo
