From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Aditya <yashsri421@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] Mentee Proposal Feedback
Date: Wed, 28 Oct 2020 09:23:47 +0100 [thread overview]
Message-ID: <CAKXUXMxv5Yw801ag6O-12--pmvoaY0yrqvJCAXvkjWvJ1bCtgg@mail.gmail.com> (raw)
In-Reply-To: <ae7f0aa5-80e6-1ae7-6763-f62791982e89@gmail.com>
On Wed, Oct 28, 2020 at 9:18 AM Aditya <yashsri421@gmail.com> wrote:
>
> On 28/10/20 11:03 am, Lukas Bulwahn wrote:
> >
> > I added some comments.
> > I suggest committing for the first three weeks to create at least five
> > new fix features in checkpatch.pl and get those patches accepted..
> >
> > Maybe you can already make a list of suggestions for automatic fix
> > features that you think are worth being implemented?
> >
> > What do you think?
> >
> > Lukas
> >
>
> I agree. I'll try to be more specific on this one.
> As I have not used this feature in past, I'd appreciate if others can
> help me regarding more issues they faced using it. This could also
> help me focus on more relevant issues.
>
Look at your evaluation and think what a suitable fix could be and
then look if that has already been implemented or not.
If not, you have a suitable task.
Lukas
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-10-28 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 9:11 [Linux-kernel-mentees] Mentee Proposal Feedback Aditya
2020-10-26 16:49 ` Lukas Bulwahn
2020-10-26 18:01 ` Aditya
2020-10-26 20:04 ` Aditya
2020-10-27 17:48 ` Aditya
2020-10-28 5:33 ` Lukas Bulwahn
2020-10-28 8:18 ` Aditya
2020-10-28 8:23 ` Lukas Bulwahn [this message]
2020-10-28 16:19 ` Aditya
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=CAKXUXMxv5Yw801ag6O-12--pmvoaY0yrqvJCAXvkjWvJ1bCtgg@mail.gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=yashsri421@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.