From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Michael Abbott <michael-W/Bzo8D1sxa8qtKVGud/9w@public.gmane.org>
Cc: 伊泽 <wxc200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Mark Brown" <broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Linux Kernel Mailing List"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report
Date: Mon, 11 May 2009 16:15:48 +0200 [thread overview]
Message-ID: <20090511141548.GB3061@pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0905111458290.6308-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
> Still, I think it would make more sense for these to be one-liners; I
> guess routine probing failures ought to be reported in a slightly
> different way. I'll see if I can figure out a sensible patch.
You might want to have a look here as I also noted once that the
pxa-driver is a bit too talkative when writing to eeproms:
http://www.mail-archive.com/linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg00324.html
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-05-11 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 7:32 [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report Michael Abbott
[not found] ` <Pine.LNX.4.64.0905060829580.24668-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-06 8:22 ` Jean Delvare
[not found] ` <20090506102202.73d6045d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-05-11 6:38 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905081102060.14384-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-11 8:56 ` Jean Delvare
2009-05-11 10:11 ` 伊泽
[not found] ` <fd6b62c10905110311w6350828tf90d9c699b73fe30-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-11 10:31 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905111126020.20970-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-11 11:28 ` Mark Brown
[not found] ` <20090511112801.GA20283-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2009-05-11 12:16 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905111314450.30347-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-11 12:23 ` Mark Brown
2009-05-11 13:29 ` 伊泽
[not found] ` <fd6b62c10905110629w6c9a641fr878351fb9217a32e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-11 14:01 ` Michael Abbott
[not found] ` <Pine.LNX.4.64.0905111458290.6308-EMtNTEpPrk39UE2ag0LVtCp2UmYkHbXO@public.gmane.org>
2009-05-11 14:15 ` Wolfram Sang [this message]
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=20090511141548.GB3061@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=broonie-GFdadSzt00ze9xe1eoZjHA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael-W/Bzo8D1sxa8qtKVGud/9w@public.gmane.org \
--cc=wxc200-Re5JQEeQqe8AvxtiuMwx3w@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).