From: Julia Lawall <julia.lawall@inria.fr>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: outreachy-kernel@googlegroups.com,
Kushal Kothari <kushalkothari285@gmail.com>,
mike.rapoport@gmail.com, mchehab@kernel.org,
sakari.ailus@linux.intel.com, gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [PATCH] staging : media : atomisp : input_system.c : fixes the error of control reaches end of non-void function [-Werror=return-type]
Date: Fri, 15 Oct 2021 16:52:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2110151648300.7123@hadrien> (raw)
In-Reply-To: <2247559.FlfiXgstMM@localhost.localdomain>
On Fri, 15 Oct 2021, Fabio M. De Francesco wrote:
> On Friday, October 15, 2021 2:04:49 PM CEST Fabio M. De Francesco wrote:
> > Hi Kushal,
> >
> > Aside from what Alison said about not accepting patches in this driver this
> > round, please note that this is not the correct way to address that
> compiler
> > warning.
> >
> > Think about it: now, whatever "state" you get from set_source_type(), you
> > always return it to the caller of input_system_configure_channel_sensor().
> >
> > By doing so, you change the logic of the function and get dead code. This
> > change makes the rest of the function code unreachable and introduces a
> huge
> > bug.
> >
> > While the patch cannot be accepted for Outreachy, think of a better
> solution
> > as you may need to make similar changes in future patches.
> >
> > Thanks and welcome,
> >
> > Fabio M. De Francesco
>
> I'm sorry, but just now I saw the reply Kieran Bingham. I'm simply restating
> what he wrote, so please disregard my email.
>
> I think that I didn't see his email because you forgot to CC linux-
> staging@lists.linux.dev and linux-kernel@vger.kernel.org.
>
> Please read again the Outreachy rules. If I'm not wrong, you should always CC
> the two mailing lists above.
The instructions say to use the following:
perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f {file}
Probably the --nol argument should not be there, because some staging
drivers have mailing lists that should see the patches. I don't know if it
is desirable for everything to go to linux-kernel@vger.kernel.org though.
This part of the application process is meant to be highly newbie
tolerant.
In any case, Alison can decide.
julia
>
> Thanks,
>
> Fabio M. De Francesco
>
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/2247559.FlfiXgstMM%40localhost.localdomain.
>
next prev parent reply other threads:[~2021-10-15 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 22:30 [PATCH] staging : media : atomisp : input_system.c : fixes the error of control reaches end of non-void function [-Werror=return-type] Kushal Kothari
2021-10-15 2:26 ` [Outreachy kernel] " Alison Schofield
2021-10-15 8:54 ` Kieran Bingham
2021-10-15 12:04 ` Fabio M. De Francesco
2021-10-15 12:18 ` Fabio M. De Francesco
2021-10-15 14:52 ` Julia Lawall [this message]
2021-10-15 15:11 ` 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=alpine.DEB.2.22.394.2110151648300.7123@hadrien \
--to=julia.lawall@inria.fr \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kushalkothari285@gmail.com \
--cc=mchehab@kernel.org \
--cc=mike.rapoport@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=sakari.ailus@linux.intel.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.