All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Berger <thorsten.berger@rub.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	deltaone@debian.org, phayax@gmail.com,
	Eugene Groshev <eugene.groshev@gmail.com>,
	Sarah Nadi <nadi@ualberta.ca>, Mel Gorman <mgorman@suse.de>,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [RFC v3 03/12] Add picosat.c (2/3)
Date: Mon, 25 Oct 2021 01:52:27 +0200	[thread overview]
Message-ID: <82bcea90-b71f-05bb-1efc-8fa623d07d96@rub.de> (raw)
In-Reply-To: <CAK7LNAR=S0tVNdQXGg+MKMK7vA-YZawhw08QfFwifxEGJRWayA@mail.gmail.com>

On 24.10.2021 11:05, Masahiro Yamada wrote:
> On Fri, Oct 22, 2021 at 10:38 PM Thorsten Berger <thorsten.berger@rub.de> wrote:
>> The second part of picosat.c
>>
>> ---
>
> Most of the patches in this series are corrupted.
>
> Both 'git am' and 'patch' failed.
>
> masahiro@grover:~/workspace/linux-kbuild$ git am
> ~/Downloads/RFC-v3-03-12-Add-picosat.c-2-3.patch
> Applying: Add picosat.c (2/3)
> error: corrupt patch at line 10
> Patch failed at 0001 Add picosat.c (2/3)
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
>
> $ patch -p1 <  ~/Downloads/RFC-v3-03-12-Add-picosat.c-2-3.patch
> patching file scripts/kconfig/picosat.c
> patch: **** malformed patch at line 82:        {
>
>
>
>
>
> Each line of the diff context should begin with
> a space, '+', or '-'.
>
> But the offending line starts with 0xc2, 0xa0.
> Strange.
>
>
>
> Could you re-check the patch format and resend?
Thanks for working on it!

Sorry for that, we probably made some stupid beginner mistakes. Patrick Franz is looking into it.
> (or can you push your branch to somewhere?)
It's here: https://github.com/delta-one/linux/tree/configfix-next
>
> One more request:
>
> Please tell me which version of picosat
> (http://fmv.jku.at/picosat/) you imported.
Picosat 965
>
> Thanks.

Best, Thorsten


  reply	other threads:[~2021-10-24 23:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 13:34 [RFC v3 00/12] kconfig: add support for conflict resolution Thorsten Berger
2021-10-22 13:35 ` [RFC v3 01/12] Add picosat.h Thorsten Berger
2021-10-22 16:57   ` Luis Chamberlain
2021-10-22 13:36 ` [RFC v3 02/12] Add picosat.c (1/3) Thorsten Berger
2021-10-22 16:58   ` Luis Chamberlain
2021-10-22 13:38 ` [RFC v3 03/12] Add picosat.c (2/3) Thorsten Berger
2021-10-22 16:59   ` Luis Chamberlain
2021-10-24  9:05   ` Masahiro Yamada
2021-10-24 23:52     ` Thorsten Berger [this message]
2021-10-22 13:39 ` [RFC v3 04/12] Add picosat.c (3/3) Thorsten Berger
2021-10-22 13:40 ` [RFC v3 05/12] Add definitions Thorsten Berger
2021-10-22 16:56   ` Luis Chamberlain
2021-10-22 13:41 ` [RFC v3 06/12] Add files for building constraints Thorsten Berger
2021-10-22 16:56   ` Luis Chamberlain
2021-10-22 13:43 ` [RFC v3 07/12] Add files for handling expressions Thorsten Berger
2021-10-22 13:44 ` [RFC v3 08/12] Add files for RangeFix Thorsten Berger
2021-10-22 13:45 ` [RFC v3 09/12] Add files with utility functions Thorsten Berger
2021-10-22 13:46 ` [RFC v3 10/12] Add tools Thorsten Berger
2021-10-22 13:47 ` [RFC v3 11/12] Add xconfig-modifications Thorsten Berger
2021-11-04  9:30   ` Masahiro Yamada
2021-10-22 13:48 ` [RFC v3 12/12] Simplify dependencies for MODULE_SIG_KEY_TYPE_RSA & MODULE_SIG_KEY_TYPE_ECDSA Thorsten Berger
2021-10-22 17:03   ` Luis Chamberlain

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=82bcea90-b71f-05bb-1efc-8fa623d07d96@rub.de \
    --to=thorsten.berger@rub.de \
    --cc=deltaone@debian.org \
    --cc=eugene.groshev@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mcgrof@suse.com \
    --cc=mgorman@suse.de \
    --cc=nadi@ualberta.ca \
    --cc=phayax@gmail.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.