Re: [PATCH 1/2] Adding document for sparse patch submit process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 10, 2017 at 3:36 PM, Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote:
> On 08/09/2017 08:27 PM, Christopher Li wrote:
>> Reference to the linux kernel patches submitting process
>> and difference to sparse.
>>
>> Signed-off-by: Christopher Li <sparse@xxxxxxxxxxx>
>> ---
>>  Documentation/submitting-patches.md | 21 +++++++++++++++++++++
>>  1 file changed, 21 insertions(+)
>>  create mode 100644 Documentation/submitting-patches.md
>>
>> diff --git a/Documentation/submitting-patches.md
>> b/Documentation/submitting-patches.md
>> new file mode 100644
>> index 0000000..f526d44
>> --- /dev/null
>> +++ b/Documentation/submitting-patches.md
>> @@ -0,0 +1,21 @@
>> +Submitting patches: the sparse version
>> +======================================
>> +
>> +Sparse use a patch submit process similar to the Linux Kernel
>
>           uses

Great Great.

That is exactly the feed back I need :-)

I will incarcerate your feed back and send out an update very soon.


>
>> +
>> +2. Sign off the patch.
>
> 3. instead of 2. ??

Yes, I can use 3.  The exact number does not matter to MD parsing,
but using 3 will make the reader less confusing.

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux