From: Johan Hovold <johan@kernel.org>
To: Octavian Purdila <octavian.purdila@intel.com>
Cc: Johan Hovold <johan@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] mfd: viperboard: allocate I/O buffer separately
Date: Mon, 22 Sep 2014 18:20:50 +0200 [thread overview]
Message-ID: <20140922162050.GL5237@localhost> (raw)
In-Reply-To: <CAE1zotJiLDWYThHL4DUpsnqm+C2anf1ri_Wr6+4kq5rn8YjDag@mail.gmail.com>
On Mon, Sep 22, 2014 at 07:19:37PM +0300, Octavian Purdila wrote:
> On Mon, Sep 22, 2014 at 7:08 PM, Johan Hovold <johan@kernel.org> wrote:
> > On Mon, Sep 22, 2014 at 05:46:52PM +0300, Octavian Purdila wrote:
> > Don't mix fixes and clean ups like this, but rather submit them as
> > separate patches.
> >
> Fair enough. Is it OK to send all of the cleanups in a single separate
> patch?
In this case, I'd say so. But do the clean-ups on top of the minimal fix
to facilitate back-porting if someone ever decides that that is needed.
Johan
prev parent reply other threads:[~2014-09-22 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 14:46 [PATCH] mfd: viperboard: allocate I/O buffer separately Octavian Purdila
2014-09-22 16:08 ` Johan Hovold
2014-09-22 16:19 ` Octavian Purdila
2014-09-22 16:20 ` Johan Hovold [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=20140922162050.GL5237@localhost \
--to=johan@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=sameo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox