All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jorge Lopez <jorgealtxwork@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] Resolve WMI query failures on some devices
Date: Thu, 9 Jun 2022 08:45:37 -0500	[thread overview]
Message-ID: <CAOOmCE_sMSe3eGudUBagDztfBa6HYDKgg8KFcp9cHEpPL4N7jg@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VeC89LEE0AnOfAKXXmrATOaNGu6RmXztaYGkXDbabokxw@mail.gmail.com>

Hi Andy,


On Thu, Jun 9, 2022 at 5:50 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Wed, Jun 8, 2022 at 11:04 PM Jorge Lopez <jorgealtxwork@gmail.com> wrote:
> >
> > Hi Andy,
> >
> > Failure to run your tool and include all the appropriate parties in
> > the review was an oversight on my part.  I will make sure it is done
> > in the following patches.
>
> Hmm... It uses get_maintainer.pl which I believe uses the MAINTAINERS
> database more or less correctly. I use the script on a daily basis.
>
> > Regarding the statement  ...
> >
> >       Please, be careful and read all comments you have been given and react
> >       to them either by explaining why it's not worth to address or with an
> >       addressed changes.
> >
> > All other comments have been addressed in the commit notes and via
> > email.
>
> I have noticed that by reading the next patch. As I mentioned there,
> it should be squashed to the first one, I never expected to see two
> patches on this topic.

This is my first year working with kernel upstream teams and reviewers
hence I am a newcomer.  For this reason, I was being cautious and
separated the changes instead of squashing them.  Please excuse my
inexperience in the matter.

>
> >   The comments addressed were
> >
> > - As a quick fix it's good, but have you had a chance to understand why
> > this failure happened in the first place?
> >
> > - Can you check my theory that is expressed in the code below?
> > - Leverage ge2maintainer tool to include all appropriate parties.
> > (See earlier comment)
> >
> > Did I address all the comments?  If not, please accept my apologies
> > and kindly point to the question(s) I need to address.
>
>
>
> --
> With Best Regards,
> Andy Shevchenko

  reply	other threads:[~2022-06-09 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 17:02 [PATCH v2 0/2] Resolve-WMI-query-failures-on-some-devices Jorge Lopez
2022-06-08 17:02 ` [PATCH v2 1/2] Resolve WMI query failures on some devices Jorge Lopez
2022-06-08 18:44   ` Andy Shevchenko
2022-06-08 21:03     ` Jorge Lopez
2022-06-09 10:49       ` Andy Shevchenko
2022-06-09 13:45         ` Jorge Lopez [this message]
2022-06-09 15:06           ` Andy Shevchenko
2022-06-08 17:02 ` [PATCH v2 2/2] Organize declaration variables Jorge Lopez
2022-06-08 18:45   ` Andy Shevchenko
2022-06-08 19:31     ` Jorge Lopez
2022-06-08 18:42 ` [PATCH v2 0/2] Resolve-WMI-query-failures-on-some-devices Andy Shevchenko
2022-06-08 19:28   ` Jorge Lopez

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=CAOOmCE_sMSe3eGudUBagDztfBa6HYDKgg8KFcp9cHEpPL4N7jg@mail.gmail.com \
    --to=jorgealtxwork@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=platform-driver-x86@vger.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 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.