linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: RDMA list <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] mlx4: Change a warning message to debug
Date: Mon, 13 Dec 2010 13:55:41 -0800	[thread overview]
Message-ID: <adazks9gwwy.fsf@cisco.com> (raw)
In-Reply-To: <20101210122759.GA28088@mtldesk30> (Eli Cohen's message of "Fri, 10 Dec 2010 14:27:59 +0200")

 > > Not sure I agree ... surely the point of this message is for the user to
 > > see it and know to update firmware?  Otherwise why print anything at
 > > all, since I'm sure you guys have already fixed the firmware and have a
 > > regression test so this bug doesn't reappear?

 > Right :-)

So what do you think -- remove the message entirely or leave it?

 - R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-12-13 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  8:06 [PATCH] mlx4: Change a warning message to debug Eli Cohen
2010-12-08 19:03 ` Roland Dreier
     [not found]   ` <adaipz4jddc.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-12-10 12:27     ` Eli Cohen
2010-12-13 21:55       ` Roland Dreier [this message]
     [not found]         ` <adazks9gwwy.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-12-14 11:26           ` Eli Cohen
2011-01-04 22:24 ` Roland Dreier

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=adazks9gwwy.fsf@cisco.com \
    --to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
    --cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).