From: Khadija Kamran <kamrankhadijadj@gmail.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
outreachy@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] staging: axis-fifo: initialize timeouts in probe only
Date: Wed, 15 Mar 2023 18:56:27 +0500 [thread overview]
Message-ID: <ZBHOi8vA/LpCyLTJ@khadija-virtual-machine> (raw)
In-Reply-To: <2168386.Az4OtozEo7@suse>
On Wed, Mar 15, 2023 at 02:13:51PM +0100, Fabio M. De Francesco wrote:
> On mercoledì 15 marzo 2023 13:32:55 CET Khadija Kamran wrote:
> > On Tue, Mar 14, 2023 at 04:57:47PM -0700, Alison Schofield wrote:
> > > My guess is that this patch gets ignored because it has a lower version
> > > number than a previous patch.
> > >
> > > Take the feedback given here, and rev to
> > > [PATCH v5] staging: axis-fifo: initialize timeouts in probe only
> > >
> > > Be sure the Changelog, below the --- explains the journey.
> > >
> > > Changes in v5:
> > >
> > > Changes in v4:
> > >
> > > Changes in v3:
> >
> > > Changes in v2:
> > Hey Alison!
>
> Hi Khadija,
>
> Please put one or two blank lines between the last message you are replying
> and the new you are writing (exactly as I'm doing here between "Hey Alison!"
> and "Hi Khadija").
>
Hey Fabio!
Sorry about that. This was pointed by Alison before and I have been
adding spaces since then. Hopefully I am doing it right this time.
> > Based on Nathan's feedback I am trying to recompile and send a patch
> > without any warnings.
>
> Great!
>
> > As suggested by Fabio, I am running "make w=1 -jX" command to see if I
> > get any warnings.
>
> I suppose that "w=1" is a typo. The option is enabled with "W=1" (capital
> case, Linux and all UNIX-like are case-sensitive).
>
Okay. I should re-run it with "W=1".
> > But it is taking a lot of time, is there any way of
> > speeding it up?
>
> What is you choice for 'X' in "-jX"?
I used "-j4".
> Did you try with the exact number of logical cores?
> Are you building into a VM with enough logical cores?
> If you are building into a VM, did you reserve enough RAM?
I am using Ubuntu 22.04.01 with the help of VM on VMware.
My machine has 13GB RAM and 2 processors(4 cores each).
> Please read carefully my questions above and try to understand your
> environment and reply, so that I can help you more effectively.
>
> > If this doesn't work then I have to follow the steps to reproduce in lkp
> > mail as you said before.
>
> The steps to reproduce will take your precious time and use more resources.
> Again, try to respond my questions.
>
> > After dealing with these warnings I will send a [PATCH v5], following
> > your instructions above.
>
> Sorry for inadvertently overlooking to warn you about to send a message to
> Greg and ask him to drop your first 3 + 1 patches. Now you are doing good by
> following what Alison suggested: send v5 and write the log of revisions under
> the three dashes (exactly how Alison explained).
>
> > Kindly, let me know if I am on the wrong track.
> > Thank you!
> >
>
> I think you are in the right track.
> Let's try to speed up your builds because you'll need to build again your
> kernel many, many times for future works.
>
Okay great! Thank you.
Regards,
Khadija
> Thanks,
>
> Fabio
>
>
next prev parent reply other threads:[~2023-03-15 13:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 18:07 [PATCH] staging: axis-fifo: initialize timeouts in probe only Khadija Kamran
2023-03-13 19:00 ` kernel test robot
2023-03-14 3:45 ` kernel test robot
2023-03-14 14:08 ` Khadija Kamran
2023-03-14 14:42 ` Nathan Chancellor
2023-03-14 15:13 ` Alison Schofield
2023-03-14 19:07 ` Fabio M. De Francesco
2023-03-14 20:43 ` Alison Schofield
2023-03-14 21:31 ` Fabio M. De Francesco
2023-03-14 23:57 ` Alison Schofield
2023-03-15 12:32 ` Khadija Kamran
2023-03-15 13:13 ` Fabio M. De Francesco
2023-03-15 13:56 ` Khadija Kamran [this message]
2023-03-15 16:44 ` Fabio M. De Francesco
2023-03-16 9:50 ` Khadija Kamran
2023-03-16 11:13 ` Fabio M. De Francesco
2023-03-16 12:03 ` Khadija Kamran
2023-03-15 13:34 ` Fabio M. De Francesco
2023-03-15 14:22 ` Khadija Kamran
2023-03-15 15:06 ` Nathan Chancellor
2023-03-15 16:24 ` Fabio M. De Francesco
2023-03-16 10:17 ` Khadija Kamran
2023-03-16 11:39 ` Fabio M. De Francesco
2023-03-16 11:55 ` Khadija Kamran
2023-03-16 7:40 ` Julia Lawall
2023-03-16 10:47 ` Khadija Kamran
2023-03-16 11:41 ` Khadija Kamran
2023-03-15 16:09 ` Alison Schofield
2023-03-15 16:42 ` Khadija Kamran
2023-03-16 10:36 ` Khadija Kamran
2023-03-16 10:51 ` Julia Lawall
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=ZBHOi8vA/LpCyLTJ@khadija-virtual-machine \
--to=kamrankhadijadj@gmail.com \
--cc=alison.schofield@intel.com \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=outreachy@lists.linux.dev \
/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