From: Joe Perches <joe@perches.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v1 0/4] mfd: reorganize Intel drivers
Date: Fri, 12 Dec 2014 02:15:57 -0800 [thread overview]
Message-ID: <1418379357.18092.44.camel@perches.com> (raw)
In-Reply-To: <1418379009.17201.61.camel@linux.intel.com>
On Fri, 2014-12-12 at 12:10 +0200, Andy Shevchenko wrote:
> On Thu, 2014-12-11 at 08:06 -0800, Joe Perches wrote:
> > On Thu, 2014-12-11 at 17:53 +0200, Andy Shevchenko wrote:
> > > This patchset creates a new folder under drivers/mfd and moves there Intel
> > > related drivers.
> >
> > Missing update of MAINTAINERS?
>
> Oh, right. I could send a follow up patch or update each patch in the
> series. What is the best approach here?
I think it'd be fine to send another patch later on
if/after this is applied.
next prev parent reply other threads:[~2014-12-12 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 15:53 [PATCH v1 0/4] mfd: reorganize Intel drivers Andy Shevchenko
2014-12-11 15:53 ` [PATCH v1 1/4] mfd: change a layout for the Intel related drivers Andy Shevchenko
2015-01-20 12:33 ` Andy Shevchenko
2014-12-11 15:53 ` [PATCH v1 2/4] mfd: intel/lpc/sch: move driver to dedicated folder Andy Shevchenko
2014-12-11 15:53 ` [PATCH v1 3/4] mfd: intel/lpc/ich: " Andy Shevchenko
2014-12-11 15:53 ` [PATCH v1 4/4] mfd: intel/pmic: " Andy Shevchenko
2014-12-11 16:06 ` [PATCH v1 0/4] mfd: reorganize Intel drivers Joe Perches
2014-12-12 10:10 ` Andy Shevchenko
2014-12-12 10:15 ` Joe Perches [this message]
2014-12-30 19:29 ` Andy Shevchenko
2015-01-20 13:48 ` Lee Jones
2015-01-20 14:16 ` Andy Shevchenko
2015-01-20 15:46 ` Lee Jones
2015-01-20 16:15 ` Andy Shevchenko
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=1418379357.18092.44.camel@perches.com \
--to=joe@perches.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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 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.