linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Szilard Fabian <szfabian@bluemarch.art>
Cc: W_Armin@gmx.de, Hans de Goede <hdegoede@redhat.com>,
	jwoithe@just42.net,  LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org
Subject: Re: [RFC PATCH v3] platform/x86/fujitsu-laptop: Add battery charge control support
Date: Fri, 16 Feb 2024 11:27:40 +0200 (EET)	[thread overview]
Message-ID: <77f71c25-a3d5-225e-9fc4-1b9d8ad3797d@linux.intel.com> (raw)
In-Reply-To: <Zc5wIViz3d8sBLHP@bluemarch.art>

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

On Thu, 15 Feb 2024, Szilard Fabian wrote:
> On Thu, Feb 15, 2024 at 12:34:00PM +0100, Ilpo Järvinen wrote:
> > Why is this posted as RFC?
>
> It's my third patch into the Linux kernel (the first two being a i8042 quirk
> table related patch) and I was not sure if everything is okay with v1/v2.
> But it looks like the patch matured enough in v3 to reach it's near final
> form and there was not too much to comment anymore. Sorry for any
> inconvenience I've caused with that.

No problem. I asked just to gauge if there was something you still planned 
to do in addition to what is there. I kind of guessed that in this case 
"RFC" mostly meant "I'm being careful here" more than that you'd have 
something you felt still missing from the patch. :-)

-- 
 i.

> Thanks for your feedback. I'll post v4 in a moment.
> 
> Regards,
> Szilard
> 
> 

  reply	other threads:[~2024-02-16  9:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 16:36 [RFC PATCH] platform/x86/fujitsu-laptop: Add battery charge control support Szilard Fabian
2024-01-29 18:00 ` [RFC PATCH v2] " Szilard Fabian
2024-01-30  2:02   ` Armin Wolf
2024-02-03  0:17     ` Szilard Fabian
2024-02-05 17:07       ` Armin Wolf
2024-02-05 23:37         ` Jonathan Woithe
2024-02-07  2:32   ` [RFC PATCH v3] " Szilard Fabian
2024-02-07  8:57     ` Hans de Goede
2024-02-08  1:56       ` Szilard Fabian
2024-02-08  9:11         ` Hans de Goede
2024-02-15 11:34     ` Ilpo Järvinen
2024-02-15 20:12       ` Szilard Fabian
2024-02-16  9:27         ` Ilpo Järvinen [this message]
2024-02-15 20:31     ` [PATCH v4] " Szilard Fabian
2024-02-18  4:47       ` Jonathan Woithe
2024-02-19 12:06       ` Ilpo Järvinen
2024-02-27 10:18         ` Ilpo Järvinen
2024-02-27 12:04           ` Szilard Fabian
2024-02-27 12:05       ` [PATCH v5] " Szilard Fabian
2024-02-27 12:53         ` Ilpo Järvinen
2024-02-27 21:47         ` Jonathan Woithe

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=77f71c25-a3d5-225e-9fc4-1b9d8ad3797d@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=W_Armin@gmx.de \
    --cc=hdegoede@redhat.com \
    --cc=jwoithe@just42.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=szfabian@bluemarch.art \
    /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).