linux-kernel - Re: [PATCH 01/26] staging: et131x: Put all .c files into one big file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Oct 2011 22:28:24 +0100
From:	Mark Einon <mark.einon@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	gregkh@...e.de, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/26] staging: et131x: Put all .c files into one big file

On 19 October 2011 21:41, Greg KH <greg@...ah.com> wrote:
> On Tue, Oct 18, 2011 at 05:07:34PM +0100, Mark Einon wrote:
>> Created one big .c file for the driver, moving the contents of all
>> driver .c files into it.
>>
>> Signed-off-by: Mark Einon <mark.einon@...il.com>
>
> Something is wrong here, when I try to apply this patch with git, I get
> the following errors:
[...]
>
> Care to resend it with the file actually deleted?  How are you
> generating this patch?
>
> And, when you resend the series, don't put the [RESEND] in the subject,
> I had to edit that out in order to apply them properly (which turned out
> to be a waste of time due to this patch not applying...)

Apologies Greg, I didn't mean to waste your time.

I've used this command to generate the patch, in order not to include
the entire file contents that have been deleted:

git format-patch -D <to-list> <patches>

I also assumed RESEND was commonly used for the purpose of resending
patches. Is this not the case?

Cheers,

Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/