From: "Pali Rohár" <pali.rohar@gmail.com>
To: Jean Delvare <jdelvare@suse.com>, Wolfram Sang <wsa@the-dreams.de>
Cc: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Michał Kępień" <kernel@kempniu.pl>,
"Steven Honeyman" <stevenhoneyman@gmail.com>,
"Valdis Kletnieks" <Valdis.Kletnieks@vt.edu>,
"Jochen Eisinger" <jochen@penguin-breeder.org>,
"Gabriele Mazzotta" <gabriele.mzt@gmail.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Mario Limonciello" <Mario_Limonciello@dell.com>,
"Alex Hung" <alex.hung@canonical.com>,
"Takashi Iwai" <tiwai@suse.de>,
linux-i2c <linux-i2c@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Platform Driver" <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v2] i2c: i801: Register optional lis3lv02d i2c device on Dell machines
Date: Sat, 27 Apr 2019 08:48:55 +0200 [thread overview]
Message-ID: <20190427064855.omawrv2vmcehsspb@pali> (raw)
In-Reply-To: <20180418114610.rohdk5mnzv4km4z2@pali>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Wednesday 18 April 2018 13:46:10 Pali Rohár wrote:
> On Thursday 08 March 2018 23:53:30 Pali Rohár wrote:
> > On Monday 26 February 2018 21:32:55 Wolfram Sang wrote:
> > >
> > > > I'm not maintainer of i2c-i801.ko, Jean Delvare & Wolfram Sang are.
> > > > Therefore instructing future contributors would be up to them.
> > >
> > > This is really Jean's realm.
> > >
> >
> > Jean, ping.
>
> Jean, gently ping again. Waiting for your maintainer response/decision
> on this problem.
Jean, one year passed without any answer. May you response to this
thread about this patch?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-04-27 6:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 13:32 [PATCH v2] i2c: i801: Register optional lis3lv02d i2c device on Dell machines Pali Rohár
2018-01-28 14:39 ` Andy Shevchenko
2018-01-28 14:45 ` Pali Rohár
2018-01-28 15:00 ` Andy Shevchenko
2018-01-31 12:03 ` Pali Rohár
2018-01-31 12:27 ` Andy Shevchenko
2018-02-12 15:30 ` Pali Rohár
2018-02-13 14:55 ` Andy Shevchenko
2018-02-13 15:00 ` Pali Rohár
2018-02-13 15:06 ` Andy Shevchenko
2018-02-13 16:50 ` Pali Rohár
2018-02-13 17:01 ` Andy Shevchenko
2018-02-13 17:05 ` Andy Shevchenko
2018-02-26 20:32 ` Wolfram Sang
2018-03-08 22:53 ` Pali Rohár
2018-04-18 11:46 ` Pali Rohár
2019-04-27 6:48 ` Pali Rohár [this message]
2019-05-28 9:19 ` Jean Delvare
2019-05-28 9:41 ` Pali Rohár
2019-05-28 9:50 ` Jean Delvare
2019-05-28 9:54 ` Pali Rohár
2019-05-28 10:00 ` Jean Delvare
2018-02-11 22:03 ` Michał Kępień
2018-02-12 15:25 ` Andy Shevchenko
2019-06-02 13:20 ` [PATCH v3] " Pali Rohár
2019-06-04 14:57 ` Jean Delvare
2019-06-04 22:30 ` Pali Rohár
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=20190427064855.omawrv2vmcehsspb@pali \
--to=pali.rohar@gmail.com \
--cc=Mario_Limonciello@dell.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alex.hung@canonical.com \
--cc=andy.shevchenko@gmail.com \
--cc=gabriele.mzt@gmail.com \
--cc=jdelvare@suse.com \
--cc=jochen@penguin-breeder.org \
--cc=kernel@kempniu.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stevenhoneyman@gmail.com \
--cc=tiwai@suse.de \
--cc=wsa@the-dreams.de \
/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).