From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, Eric Miao <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Daniel Mack <daniel@zonque.org>,
Marek Vasut <marek.vasut@gmail.com>,
Philipp Zabel <philipp.zabel@gmail.com>,
Paul Parsons <lost.distance@yahoo.com>,
Jonathan Cameron <jic23@cam.ac.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: pxa: move header file out of deprecated i2c folder
Date: Sun, 29 Oct 2017 21:34:00 +0100 [thread overview]
Message-ID: <87y3ntlmmf.fsf@belgarion.home> (raw)
In-Reply-To: <20171029175257.dfmf5642zfszoxe3@ninjato> (Wolfram Sang's message of "Sun, 29 Oct 2017 18:52:57 +0100")
Wolfram Sang <wsa@the-dreams.de> writes:
Hi Wolfram,
> Wouldn't it be even cleaner if patch 1 & 2 above would be swapped? First
> move the chunk, then rename the file?
Yeah sure.
> And is there a branch I should base this on? Currently, I am thinking of
> basing this patch on for-next and then submit it around rc1 time.
>
> Does that make sense to you?
Yeah that's good. I usually make my pull requests around -rc5, that gives enough
time to review and test on my side.
As for the base, for-next is exactly pxa/for-next as no patches are pending, so
go ahead and base your work on it please.
Cheers.
--
Robert
prev parent reply other threads:[~2017-10-29 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 16:43 [PATCH] i2c: pxa: move header file out of deprecated i2c folder Wolfram Sang
2017-10-13 20:59 ` Robert Jarzmik
2017-10-13 21:45 ` Wolfram Sang
2017-10-29 17:52 ` Wolfram Sang
2017-10-29 20:34 ` Robert Jarzmik [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=87y3ntlmmf.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=daniel@zonque.org \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lost.distance@yahoo.com \
--cc=marek.vasut@gmail.com \
--cc=philipp.zabel@gmail.com \
--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).