From: Menna Mahmoud <eng.mennamahmoud.mm@gmail.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
outreachy@lists.linux.dev, vireshk@kernel.org, johan@kernel.org,
elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: greybus: Fix Alignment with parenthesis
Date: Sat, 11 Mar 2023 16:57:29 +0200 [thread overview]
Message-ID: <59077252-02e4-dd43-77b5-2d2cfd114762@gmail.com> (raw)
In-Reply-To: <e0d7928e-854e-4d10-a90f-db87a7d60569@kili.mountain>
On ١١/٣/٢٠٢٣ ١٦:٢٣, Dan Carpenter wrote:
> On Sat, Mar 11, 2023 at 04:06:51PM +0200, Menna Mahmoud wrote:
>> according to Alex feedback
>>
>> " I think this type of alignment is not a major problem,
>> and alignment isn't done this way in general in this
>> driver, it's probably OK to keep it that way. - Alex "
>>
>>
>> ,I won't resubmit these patches, right?
> Yeah. Find something else to fix.
>
> I feel like in outreachy and similar that people send a first patch and
> then they get a bunch of different feedback. And it's like checkpatch
> is complaining and it's staging code so probably the code is actually
> ugly in a way. But often it's better to abandon the project instead of
> getting obsessed with it. Zoom out a bit. Find something else where
> it's obvious how to improve the code from a readability perspective.
>
> People are giving you feedback to help you and not because they are
> about that particular line of code. They won't care if you work on
> something else instead.
>
> regards,
> dan carpenter
Got it, thanks Dan.
>
next prev parent reply other threads:[~2023-03-11 14:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 15:51 [PATCH 1/2] staging: greybus: Fix Alignment with parenthesis Menna Mahmoud
2023-03-10 15:51 ` [PATCH 2/2] " Menna Mahmoud
2023-03-11 8:57 ` Julia Lawall
2023-03-11 12:50 ` Menna Mahmoud
2023-03-10 16:16 ` [PATCH 1/2] " Alex Elder
2023-03-10 19:29 ` Menna Mahmoud
2023-03-11 8:59 ` Julia Lawall
2023-03-11 12:52 ` Menna Mahmoud
2023-03-11 12:55 ` Julia Lawall
2023-03-11 12:57 ` Menna Mahmoud
2023-03-11 14:06 ` Menna Mahmoud
2023-03-11 14:23 ` Dan Carpenter
2023-03-11 14:26 ` Dan Carpenter
2023-03-11 14:57 ` Menna Mahmoud [this message]
2023-03-11 14:38 ` Julia Lawall
2023-03-11 14:58 ` Menna Mahmoud
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=59077252-02e4-dd43-77b5-2d2cfd114762@gmail.com \
--to=eng.mennamahmoud.mm@gmail.com \
--cc=elder@kernel.org \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=vireshk@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;
as well as URLs for NNTP newsgroup(s).