From: viniciustinti@gmail.com (Vinícius Tinti)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Can I submit simple patches like this to the primary ML?
Date: Thu, 29 Jan 2015 01:48:43 -0200 [thread overview]
Message-ID: <20150129034843.GA15423@eudyptula> (raw)
This is a simple patch that initializes a function with NULL to avoid some
compiler warnings. In such cases should I proceed as a normal patch or it is
better to send to another ML like to one for trivial patches?
Thanks,
Tinti
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-x86-LLVMLinux-Fix-uninitialized-function-do_reloc.patch
Type: text/x-diff
Size: 1065 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150129/55db914e/attachment-0001.bin
next reply other threads:[~2015-01-29 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 3:48 Vinícius Tinti [this message]
2015-01-29 4:08 ` Can I submit simple patches like this to the primary ML? Greg KH
2015-01-29 4:16 ` Vinícius Tinti
2015-01-29 5:07 ` Greg KH
2015-01-29 11:27 ` Vinícius Tinti
2015-01-29 11:39 ` Peter Senna Tschudin
2015-01-29 14:19 ` Greg KH
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=20150129034843.GA15423@eudyptula \
--to=viniciustinti@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).