From: Jonas Gorski <jogo@openwrt.org>
To: Mark Brown <broonie@kernel.org>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
Paul Bolle <pebolle@tiscali.nl>,
ziegler@cs.fau.de, linux-kernel@vger.kernel.org
Subject: Re: spi/bcm63xx: unknown CONFIG_BIG_ENDIAN
Date: Tue, 15 Sep 2015 15:34:17 +0200 [thread overview]
Message-ID: <55F81E59.70703@openwrt.org> (raw)
In-Reply-To: <20150915084012.GB11268@sirena.org.uk>
On 15.09.2015 10:40, Mark Brown wrote:
> On Tue, Sep 15, 2015 at 09:40:30AM +0200, Jonas Gorski wrote:
>
>> Mark? If you can drop patches 2 to 4 that would be easiest for me, but if
>> you don't do rebases on your for-next branch, then I'll rewrite the
>> patches to apply on top of the already applied old versions and send a v3.
>
> No, please submit incremental modifications as incremental
> modifications.
IS there anything I can do to avoid this happining again, like a patchwork
where I can mark my older versions as superseded? I admit I didn't expect
partial application of the (old) series.
Jonas
next prev parent reply other threads:[~2015-09-15 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 6:24 spi/bcm63xx: unknown CONFIG_BIG_ENDIAN Valentin Rothberg
2015-09-15 7:40 ` Jonas Gorski
2015-09-15 8:40 ` Mark Brown
2015-09-15 13:34 ` Jonas Gorski [this message]
2015-09-15 14:07 ` Mark Brown
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=55F81E59.70703@openwrt.org \
--to=jogo@openwrt.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=valentinrothberg@gmail.com \
--cc=ziegler@cs.fau.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 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.