From: Jean Delvare <khali@linux-fr.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [jdelvare-staging:i2c-for-linus 9/15] drivers/input/keyboard/adp5588-keys.c:52:19: error: field
Date: Sun, 21 Oct 2012 12:16:59 +0000 [thread overview]
Message-ID: <20121021141659.4dd53d00@endymion.delvare> (raw)
In-Reply-To: <20121009092343.7572fb53@endymion.delvare>
On Sun, 21 Oct 2012 09:48:49 +0800, Fengguang Wu wrote:
> On Tue, Oct 16, 2012 at 09:19:41AM +0200, Jean Delvare wrote:
> > I sent you a patch yesterday which should fix the issue:
> > http://khali.linux-fr.org/devel/linux-3/jdelvare-i2c/i2c-i801-02-fix-gpiolib-dependency.patch
> > It's in linux-next already. Can you please test it and confirm it does
> > fix the issue?
>
> Hi Jean, I just sent you another report. I found that it can still be
> reproduced in upstream 3.7-rc2 and linux-next 20121019.
It turns out that linux-next no longer seems to include my i2c patches.
Stephen, can you please check?
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2012-10-21 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 7:23 [jdelvare-staging:i2c-for-linus 9/15] drivers/i2c/busses/i2c-i801.c:1014:21: error: dereferenci Jean Delvare
2012-10-15 9:13 ` [jdelvare-staging:i2c-for-linus 9/15] drivers/tty/serial/max310x.c:277:19: error: field 'gpio' Jean Delvare
2012-10-16 7:19 ` [jdelvare-staging:i2c-for-linus 9/15] drivers/input/keyboard/adp5588-keys.c:52:19: error: field Jean Delvare
2012-10-21 12:16 ` Jean Delvare [this message]
2012-10-21 14:19 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2012-10-08 7:14 [jdelvare-staging:i2c-for-linus 9/15] drivers/i2c/busses/i2c-i801.c:1014:21: error: dereferencing po Fengguang Wu
2012-10-21 1:48 ` [jdelvare-staging:i2c-for-linus 9/15] drivers/input/keyboard/adp5588-keys.c:52:19: error: field Fengguang Wu
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=20121021141659.4dd53d00@endymion.delvare \
--to=khali@linux-fr.org \
--cc=kernel-janitors@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