All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: outreachy@lists.linux.dev,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8] staging: axis-fifo: initialize timeouts in init only
Date: Mon, 20 Mar 2023 17:55:20 +0100	[thread overview]
Message-ID: <3648719.TKLx3GfHUD@suse> (raw)
In-Reply-To: <ZBhvU/USP0es8e4P@khadija-virtual-machine>

On lunedì 20 marzo 2023 15:36:03 CET Khadija Kamran wrote:
> On Mon, Mar 20, 2023 at 02:38:24PM +0100, Fabio M. De Francesco wrote:
> > On lunedì 20 marzo 2023 07:34:04 CET Khadija Kamran wrote:
> > > On Fri, Mar 17, 2023 at 11:29:25AM +0100, Fabio M. De Francesco wrote:
> > > > Khadija,
> > > > 
> > > > Congratulations for having your first patch in Linux, via Greg's 
staging
> > > > tree.
> > > > 
> > > > It will take some time before it reaches mainline, although it is
> > > > already on its way to get upstream.
> > > 
> > > [snip]
> > >
> > I'm confused by this statement. Can you please rephrase?
> > 
> > > Am I getting it right?
> > 
> > Not sure, it depends on what you meant with the previous phrase.
> 
> As you said above that the commit message makes the reader miss the
> permission details, so should we write more about permissions in the
> description?

No. Greg took your patch as is.
No new versions for patches that Maintainers (i.e., Greg Kroah-Hartman for 
drivers/staging and several other subsystems and drivers) already applied.

We've been discussing this topic after Greg had already taken your patch only 
for the purpose to clarify to you why he suggested a better commit message. 
However, he suggested that better message while stating that he prefers to 
take your patch as is to give you time to work on something new.

I suppose that you received the two automated messages, the first which 
communicates that your patch has been applied to his staging-test tree and the 
second which says that it has moved forward to the next step, which is the 
staging-next tree. I saw those messages in Cc because I put my "Reviewed-by" 
tag to your patch, so I know you had them.

Fabio

P.S.: Today I sent you an off-list message. Please locate it and reply.

> > > Thank you!
> > > 
> > > Regards,
> > > Khadija
> > 
> > You're welcome!
> > 
> > So, thanks for working on this patch as long as it takes to get it done.
> > 
> > I think the lesson to be learned is that in our community there are 
barriers
> > to the entry of substandard products and therefore people have to do their
> > best if they really want to see their work applied.
> 
> Yes, you are right. Due to this reason, the whole process is making me
> learn a lot. I am really glad to be a part of it ^-^
> 
> > These tasks are not for the "faints of heart" :-)
> > 
> > Fabio
> 
> Regards,
> Khadija :)





  reply	other threads:[~2023-03-20 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 20:09 [PATCH v8] staging: axis-fifo: initialize timeouts in init only Khadija Kamran
2023-03-17  7:13 ` Greg Kroah-Hartman
2023-03-17  8:58   ` Fabio M. De Francesco
2023-03-20  6:17     ` Khadija Kamran
2023-03-20  6:09   ` Khadija Kamran
2023-03-17 10:29 ` Fabio M. De Francesco
2023-03-20  6:34   ` Khadija Kamran
2023-03-20 13:38     ` Fabio M. De Francesco
2023-03-20 14:36       ` Khadija Kamran
2023-03-20 16:55         ` Fabio M. De Francesco [this message]
2023-03-20 17:05           ` Khadija Kamran

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=3648719.TKLx3GfHUD@suse \
    --to=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kamrankhadijadj@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --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 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.