From: Julia Lawall <julia.lawall@lip6.fr>
To: linux-kernel@vger.kernel.org, airlied@linux.ie,
netdev@vger.kernel.org, arnd@arndb.de, joern@logfs.org,
chris.mason@fusionio.com, m@bues.ch, jejb@parisc-linux.org,
faisal.latif@intel.com, neilb@suse.de,
gregkh@linuxfoundation.org, JBottomley@parallels.com,
swise@chelsio.com, achim_leubner@adaptec.com, swise@chelsio.com,
tytso@mit.edu
Cc: dri-devel@lists.freedesktop.org, jason.wessel@windriver.com,
kgdb-bugreport@lists.sourceforge.net,
Prasad Joshi <prasadjoshi.linux@gmail.com>,
logfs@logfs.org, linux-btrfs@vger.kernel.org,
Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, Roland Dreier <roland@kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
hal.rosenstock@gmail.com, linux-rdma@vger.kernel.org,
linux-raid@vger.kernel.org, linux-usb@vger.kernel.org,
linux-scsi@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: merging printk and WARN
Date: Sun, 4 Nov 2012 21:25:53 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1211042120200.1960@localhost6.localdomain6> (raw)
It looks like these patches were not a good idea, because in each case the
printk provides an error level, and WARN then provides another one.
Sorry for the noise.
julia
next reply other threads:[~2012-11-04 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 20:25 Julia Lawall [this message]
2012-11-05 15:42 ` merging printk and WARN David Sterba
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=alpine.DEB.2.02.1211042120200.1960@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=JBottomley@parallels.com \
--cc=achim_leubner@adaptec.com \
--cc=adilger.kernel@dilger.ca \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=chris.mason@fusionio.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=faisal.latif@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hal.rosenstock@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=jejb@parisc-linux.org \
--cc=joern@logfs.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=logfs@logfs.org \
--cc=m@bues.ch \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=prasadjoshi.linux@gmail.com \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=swise@chelsio.com \
--cc=tytso@mit.edu \
/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