From: Jonathan Corbet <corbet@lwn.net>
To: Hunter Lannon <kindlehl@osuosl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Easy Kernel Patch
Date: Thu, 20 Dec 2018 07:03:17 -0700 [thread overview]
Message-ID: <20181220070317.5403f546@lwn.net> (raw)
In-Reply-To: <CAPdqyfnAJf1dMCAL4SFFM40p_zn5tmUTkdfvVknCHeGLSUEPLQ@mail.gmail.com>
On Wed, 19 Dec 2018 22:47:18 -0800
Hunter Lannon <kindlehl@osuosl.org> wrote:
> This is my first patch submitted. I hope I can finally say I have a
> commit in the Linux source code :)
I expect you'll get there, but this patch won't be the one that crosses
the bar for you. Here's some suggestions for how to do it successfully
next time:
- Read Documentation/process/submitting-patches.rst all the way through.
There's a lot of information there that would have helped you to avoid
the errors made here.
- Use scripts/get_maintainer.pl to be sure that you direct your patches
to the correct maintainer(s) and lists. A patch just sent to LKML is
unlikely to come to the attention of the people who need to see it.
- Please send patches inline rather than as attachments.
With regard to the patch itself:
> From 1ce6365d07c734cea9965d3135dd64e2641021ef Mon Sep 17 00:00:00 2001
> From: kindlehl <kindlehl@osuosl.org>
> Date: Wed, 19 Dec 2018 22:36:22 -0800
> Subject: [PATCH] Removed twin forward-declaration of struct device
Patches should always have an informative changelog saying *why* your
change improves the kernel. Removing a redundant declaration certainly
does that, but you need to say so.
> Signed-off-by: kindlehl <kindlehl@osuosl.org>
The signoff line needs your full and real name.
> ---
> include/linux/pm.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/include/linux/pm.h b/include/linux/pm.h
> index e723b78d8357..d33147db9400 100644
> --- a/include/linux/pm.h
> +++ b/include/linux/pm.h
> @@ -51,8 +51,6 @@ static inline void pm_vt_switch_unregister(struct device *dev)
> * Device power management
> */
>
> -struct device;
> -
> #ifdef CONFIG_PM
> extern const char power_group_name[]; /* = "power" */
> #else
> --
> 2.19.1
Fix those up and submit the patch properly, and I see no reason why it
would not be accepted.
Thanks for working to improve the kernel!
jon
prev parent reply other threads:[~2018-12-20 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 6:47 Hunter Lannon
2018-12-20 14:03 ` Jonathan Corbet [this message]
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=20181220070317.5403f546@lwn.net \
--to=corbet@lwn.net \
--cc=kindlehl@osuosl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®