From: Eugeniu Rosca <roscaeugeniu@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/6] kconfig: re-sync with Linux 4.17-rc4
Date: Sat, 12 May 2018 23:17:51 +0200 [thread overview]
Message-ID: <20180512211751.GA3071@example.com> (raw)
In-Reply-To: <20180512193147.GA16557@x230>
Hi Petr,
On Sat, May 12, 2018 at 09:31:48PM +0200, Petr Vorel wrote:
> Hi Eugeniu,
>
> > Hello Petr,
>
> > On Sat, May 12, 2018 at 08:25:56PM +0200, Petr Vorel wrote:
>
> > > When applied all 6 patches, I got several errors (see bellow).
> > > I tested in on 2 distros (Debian unstable and openSUSE Tumbleweed).
> > > The code I applied is here, did I make error when applying patches?
> > > https://github.com/pevik/u-boot/tree/eugeniu/kconfig.v2
>
> > I checked your branch and got some interesting conclusions.
> > Here is the diff between my and your version of commit ("kconfig:
> > re-sync with Linux 4.17-rc4"):
>
> > $ git diff <eugeniu> <petr>
> > scripts/kconfig/tests/auto_submenu/expected_stdout | 14 +++++++-------
> > scripts/kconfig/tests/choice/oldask0_expected_stdout | 14 +++++++-------
> > scripts/kconfig/tests/choice/oldask1_expected_stdout | 12 ++++++------
> > scripts/kconfig/tests/new_choice_with_dep/expected_stdout | 4 ++--
> > 4 files changed, 22 insertions(+), 22 deletions(-)
>
> > Here is the same diff ignoring whitespace:
>
> > $ git diff -w <eugeniu> <petr>
> > scripts/kconfig/tests/auto_submenu/expected_stdout | 0
> > scripts/kconfig/tests/choice/oldask0_expected_stdout | 0
> > scripts/kconfig/tests/choice/oldask1_expected_stdout | 0
> > scripts/kconfig/tests/new_choice_with_dep/expected_stdout | 0
> > 4 files changed, 0 insertions(+), 0 deletions(-)
>
> > So, it seems like all the trailing white-space from above files
> > disappeared on your branch, after applying the patches from the
> > email client (who did this?...).
I hope I wasn't too harsh here. By "who" I meant the exact component or
script in your workflow which dropped the trailing spaces. By knowing
it, we could also improve our own workflows, which is a positive of
going through this issue IMHO.
> OK, my fault, I'm sorry. Applying first patch as 'git am --whitespace=warn 1.mbox' fixes
> that => make testconfig works.
No worries.
> Yes I applied patches with mutt (I usually use pwclient, but somehow I didn't find your v2
> in patchwork [1], nor even in ML [2]. Have I overlook something.
>
> [1] https://patchwork.ozlabs.org/project/uboot/list/
> [2] https://lists.denx.de/pipermail/u-boot/2018-May/date.html
I think I'm subscribed to U-boot mailing list with only one of my email
addresses. The messages arriving from another one are delayed a bit
since they have to be approved by moderators.
Thanks,
Eugeniu.
next prev parent reply other threads:[~2018-05-12 21:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 17:13 [U-Boot] [PATCH v2 1/6] kconfig: re-sync with Linux 4.17-rc4 Eugeniu Rosca
2018-05-12 17:13 ` [U-Boot] [PATCH v2 2/6] board: eets: pdu001: Fix wrong default value in Kconfig Eugeniu Rosca
2018-05-12 17:13 ` [U-Boot] [PATCH v2 3/6] scripts/dtc: Update to upstream version v1.4.5-6-gc1e55a5513e9 Eugeniu Rosca
2018-05-13 22:00 ` Simon Glass
2018-05-16 1:54 ` Masahiro Yamada
2018-05-16 11:51 ` Eugeniu Rosca
2018-05-12 17:13 ` [U-Boot] [PATCH v2 4/6] scripts/dtc: Update to upstream version v1.4.6-9-gaadd0b65c987 Eugeniu Rosca
2018-05-13 22:00 ` Simon Glass
2018-05-13 22:45 ` Eugeniu Rosca
2018-05-14 19:52 ` Simon Glass
2018-05-15 13:46 ` Eugeniu Rosca
2018-05-15 16:05 ` Simon Glass
2018-05-16 1:49 ` Masahiro Yamada
2018-05-12 17:13 ` [U-Boot] [PATCH v2 5/6] scripts/dtc: Re-sync with Linux 4.17-rc4 Eugeniu Rosca
2018-05-15 14:06 ` Eugeniu Rosca
2018-05-15 16:05 ` Simon Glass
2018-05-16 1:48 ` Masahiro Yamada
2018-05-12 17:13 ` [U-Boot] [PATCH v2 6/6] sandbox: dts: test: Fix wrong aliases property names Eugeniu Rosca
2018-05-13 22:00 ` Simon Glass
2018-05-12 18:25 ` [U-Boot] [PATCH v2 1/6] kconfig: re-sync with Linux 4.17-rc4 Petr Vorel
2018-05-12 19:17 ` Eugeniu Rosca
2018-05-12 19:31 ` Petr Vorel
2018-05-12 21:17 ` Eugeniu Rosca [this message]
2018-05-13 13:52 ` Masahiro Yamada
2018-05-13 20:43 ` Eugeniu Rosca
2018-05-14 19:35 ` Petr Vorel
2018-05-16 1:59 ` Masahiro Yamada
2018-05-16 5:09 ` Petr Vorel
2018-05-16 8:24 ` Eugeniu Rosca
2018-05-16 11:27 ` Eugeniu Rosca
2018-05-19 12:21 ` Eugeniu Rosca
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=20180512211751.GA3071@example.com \
--to=roscaeugeniu@gmail.com \
--cc=u-boot@lists.denx.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