mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Jorge Lopez" <jorgealtxwork@gmail.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Mark Pearson" <mpearson-lenovo@squebb.ca>,
	"Thomas Weißschuh" <thomas@t-8ch.de>
Cc: Linux x86 Platform Drivers <platform-driver-x86@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v7] Introduction-of-HP-BIOSCFG-driver-documentation
Date: Thu, 6 Apr 2023 16:08:11 +0200	[thread overview]
Message-ID: <565e6575-91f7-9ca2-1505-17527b95a816@redhat.com> (raw)
In-Reply-To: <CAOOmCE-5NHkYcmBP1GGpr=sEoxF9jkjj1LevekEm8R0wbrM4xQ@mail.gmail.com>

Hi All,

FWIW I have been reading along with both the v6 and
this v7 posting.

Thomas, Mark, thank you for your review / feedback
on this series.

On 4/4/23 15:37, Jorge Lopez wrote:
> Hi Bagas,
> 
>>
>> Where is the rest of patches if this is a series? Had they been merged?
>>
> 
> There is only one change as requested by  Thomas Weißschuh
> 
>> Feel free to ONLY submit the patch with the documentation for the next
>> revision. Then we can nail down the interface and initial functionality
>> and you don't always have to adapt the code to the changing interface.
> 
> Perhaps, I misunderstood Thomas request.   I will address a few other
> comments and will submit all files again.

I think that Thomas' suggestion to first focus on getting
the userspace API right and then implement the agreed
upon API is a good idea.

So for the next version just post only the documentation
patch again please.

Note it is not the intention to merge just the documentation
patch without merging the code first.

The idea is to first nail the API down and then modify
the code once to implement the agreed upon API.

Then once the API has been agreed upon post newer
versions which also include the code again.

And then once people are also happy with the code
we can merge both the code + documentation in one go.

Regards,

Hans







> 
> Regards,
> 
> Jorge
> 


  reply	other threads:[~2023-04-06 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 21:15 Jorge Lopez
2023-04-04  2:33 ` Bagas Sanjaya
2023-04-04 13:37   ` Jorge Lopez
2023-04-06 14:08     ` Hans de Goede [this message]
2023-04-14 15:13       ` Jorge Lopez
2023-04-04 14:56   ` Thomas Weißschuh
2023-04-04 17:23 ` Thomas Weißschuh
2023-04-04 20:24   ` Jorge Lopez
2023-04-11 16:16     ` Thomas Weißschuh 
2023-04-11 20:26       ` 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=565e6575-91f7-9ca2-1505-17527b95a816@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=bagasdotme@gmail.com \
    --cc=jorgealtxwork@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpearson-lenovo@squebb.ca \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=thomas@t-8ch.de \
    /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

all inboxes | Powered by JetHome®