From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Current I2C workflow
Date: Tue, 19 Mar 2013 09:44:52 +0100 [thread overview]
Message-ID: <20130319084442.GA3170@katana> (raw)
Hi,
working on the transparency thing here regarding the current I2C
workflow. I am currently on, well, let's call it something between
holiday and retreat. I will work on (hopefully all) pending I2C patches
half-time until Friday and then probably disappear for about 3 weeks
again. Disappearing means I will lurk the list for urgent patches and
handle them, but will pass the other ones for later handling. So, please
make sure to emphasize urgent patches.
For a few weeks now, the I2C list is monitored by patchwork [1] (Thanks,
Jeremy!), which should make sure that no patches are forgotten. I do use
the status field, so this list is a good place to check if you wonder
what happened to your patch. I will send replies explaining my
decisions, nonetheless.
People reviewing patches from each other are much appreciated and will
help the process.
And to make clear after some email confusion: wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org is the
preferred email address for my kernel related stuff.
Off to work,
Wolfram
[1] http://patchwork.ozlabs.org/project/linux-i2c/list/
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Current I2C workflow
Date: Tue, 19 Mar 2013 09:44:52 +0100 [thread overview]
Message-ID: <20130319084442.GA3170@katana> (raw)
Hi,
working on the transparency thing here regarding the current I2C
workflow. I am currently on, well, let's call it something between
holiday and retreat. I will work on (hopefully all) pending I2C patches
half-time until Friday and then probably disappear for about 3 weeks
again. Disappearing means I will lurk the list for urgent patches and
handle them, but will pass the other ones for later handling. So, please
make sure to emphasize urgent patches.
For a few weeks now, the I2C list is monitored by patchwork [1] (Thanks,
Jeremy!), which should make sure that no patches are forgotten. I do use
the status field, so this list is a good place to check if you wonder
what happened to your patch. I will send replies explaining my
decisions, nonetheless.
People reviewing patches from each other are much appreciated and will
help the process.
And to make clear after some email confusion: wsa@the-dreams.de is the
preferred email address for my kernel related stuff.
Off to work,
Wolfram
[1] http://patchwork.ozlabs.org/project/linux-i2c/list/
next reply other threads:[~2013-03-19 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 8:44 Wolfram Sang [this message]
2013-03-19 8:44 ` Current I2C workflow Wolfram Sang
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=20130319084442.GA3170@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.