linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bbpetkov@yahoo.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: Tejun Heo <htejun@gmail.com>, Borislav Petkov <bbpetkov@yahoo.de>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/n] libata-core.c conversion to new debugging scheme, part 1 (25% done)
Date: Fri, 2 Jun 2006 09:32:32 +0200	[thread overview]
Message-ID: <20060602073232.GA8402@gollum.tnic> (raw)
In-Reply-To: <20060601061433.GC5869@havoc.gtf.org>

On Thu, Jun 01, 2006 at 02:14:33AM -0400, Jeff Garzik wrote:
> The ata_msg_xxx level and KERN_xxx level are not perfectly mapped, nor
> should they be, so the proposed scheme may not work out once we have all
> the message levels integrated.

How about the folowing mapping for ATA-to-printk debugging levels:

ATA_MSG_DRV		----> KERN_INFO
ATA_MSG_INFO

ATA_MSG_PROBE	----> KERN_DEBUG
ATA_MSG_MALLOC
ATA_MSG_CTL
ATA_MSG_INTR

since those are in their nature debugging infos containing ENTER/EXIT
function_name calls

ATA_MSG_WARN	----> KERN_WARNING

ATA_MSG_ERR		----> KERN_ERR

but this I could do after the whole conversion thing is done so we have the new
dbg infrastructure first.

Regards,
	Boris.

	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de


  reply	other threads:[~2006-06-02  7:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31  5:46 [PATCH 1/n] libata-core.c conversion to new debugging scheme, part 1 (25% done) Borislav Petkov
2006-05-31  6:39 ` Jeff Garzik
2006-06-01  5:38   ` Borislav Petkov
2006-06-01  6:09     ` Tejun Heo
2006-06-01  6:14       ` Jeff Garzik
2006-06-02  7:32         ` Borislav Petkov [this message]
2006-06-01  6:44       ` Borislav Petkov
2006-06-12  3:11     ` Jeff Garzik
2006-06-12  3:48 ` Jeff Garzik

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=20060602073232.GA8402@gollum.tnic \
    --to=bbpetkov@yahoo.de \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.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).