From: Greg KH <greg@kroah.com>
To: Santosh Sivaraj <santosh@fossix.org>
Cc: William Tambe <tambewilliam@gmail.com>, kernelnewbies@kernelnewbies.org
Subject: Re: For a bug in lib/vsprintf.c where should a patch be sent to ?
Date: Mon, 6 Jul 2020 09:41:57 +0200 [thread overview]
Message-ID: <20200706074157.GA1950243@kroah.com> (raw)
In-Reply-To: <8736655t6h.fsf@santosiv.in.ibm.com>
On Mon, Jul 06, 2020 at 06:57:34AM +0530, Santosh Sivaraj wrote:
> William Tambe <tambewilliam@gmail.com> writes:
>
> > On Sun, Jul 5, 2020 at 8:40 PM William Tambe <tambewilliam@gmail.com> wrote:
> >>
> >> For a bug in lib/vsprintf.c where should a patch be sent to ?
> >
> > The bug is in kernel/kallsyms.c instead.
> >
> > So for a bug in kernel/kallsyms.c, where should a patch be sent to ?
> >
>
> You can use the 'get_maintainer.pl' script in the kernel tree to identify the
> list and maintainers.
>
> ./scripts/get_maintainer.pl kernel/kallsyms.c
>
>
> But in general you can send it to linux-kernel@vger.kernel.org.
If you only do that, it will be ignored, use the output of
get_maintainer.pl on your patch to get the proper list of people and
mailing lists.
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-07-06 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 0:40 For a bug in lib/vsprintf.c where should a patch be sent to ? William Tambe
2020-07-06 0:42 ` William Tambe
2020-07-06 1:27 ` Santosh Sivaraj
2020-07-06 7:41 ` Greg KH [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=20200706074157.GA1950243@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=santosh@fossix.org \
--cc=tambewilliam@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 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).