From: Alexey Klimov <klimov.linux@gmail.com>
To: David Ellingsworth <david@identd.dyndns.org>
Cc: video4linux-list@redhat.com
Subject: Re: [patch] radio-mr800: remove warn- and err- messages
Date: Mon, 03 Nov 2008 01:52:44 +0300 [thread overview]
Message-ID: <1225666364.16097.24.camel@tux.localhost> (raw)
In-Reply-To: <30353c3d0810291012y5c9a4c54x480fdb0fa807dd0c@mail.gmail.com>
Hello, all
On Wed, 2008-10-29 at 13:12 -0400, David Ellingsworth wrote:
> > you want my ack, you have the following options:
> >
> > 1. Use the same name used in the usb_driver struct
> > 2. Remove the name altogether
> >
> > If I were writing it, I'd do the following:
> >
> > #define DRVNAME "radio-mr800"
> > #define amradio_dev_err(dev, fmt, arg...) dev_err(dev, DRVNAME fmt, ##arg)
> > #define amradio_dev_warn(dev, fmt, arg...) dev_warn(dev, DRVNAME fmt, ##arg)
> Minor correction here ^^^^^
>
> It should be:
> #define amradio_dev_err(dev, fmt, arg...) dev_err(dev, DRVNAME ": " fmt, ##arg)
> #define amradio_dev_warn(dev, fmt, arg...) dev_warn(dev, DRVNAME ": "
> fmt, ##arg)
>
> - David Ellingsworth
You idea is great. I made patch, but have few questions.
May i use " - " in amradio_dev_info for example, instead of
using ..DRVNAME ": " fmt.. in defined macros? There are a lot of ":" in
messages if using ":".
May i use amradio_dev_info for cases where i want
&radio->videodev->dev ? And may i use usual dev_warn where intf->dev is
more apropriate ? Or you want me to use amradio_dev_warn macroses
everywhere ?
David, what do you think ?
Best regards,
Alexey Klimov
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-11-02 22:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 18:46 [patch] radio-mr800: remove warn- and err- messages Alexey Klimov
2008-10-16 19:17 ` David Ellingsworth
2008-10-16 19:29 ` Michael Krufky
2008-10-19 14:58 ` Alexey Klimov
2008-10-20 0:11 ` David Ellingsworth
2008-10-28 18:05 ` Alexey Klimov
2008-10-29 3:17 ` Douglas Schilling Landgraf
2008-10-29 17:08 ` David Ellingsworth
2008-10-29 17:12 ` David Ellingsworth
2008-11-02 22:52 ` Alexey Klimov [this message]
2008-11-03 16:02 ` Alexey Klimov
2008-11-03 16:19 ` David Ellingsworth
[not found] ` <490F2AE8.2060002@personnelware.com>
2008-11-03 17:01 ` David Ellingsworth
2008-11-03 17:24 ` Alexey Klimov
2008-11-03 17:36 ` David Ellingsworth
2008-11-03 17:51 ` Alexey Klimov
2008-11-03 18:21 ` David Ellingsworth
2008-11-04 15:02 ` [PATCH 1/1] radio-mr800: remove warn, info and err messages Alexey Klimov
2008-11-04 19:54 ` David Ellingsworth
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=1225666364.16097.24.camel@tux.localhost \
--to=klimov.linux@gmail.com \
--cc=david@identd.dyndns.org \
--cc=video4linux-list@redhat.com \
/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