All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Haixu Cui <quic_haixcui@quicinc.com>,
	virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org,
	harald.mommer@opensynergy.com, broonie@kernel.org,
	qiang4.zhang@linux.intel.com, viresh.kumar@linaro.org
Cc: quic_ztu@quicinc.com
Subject: [virtio-comment] Re: [virtio-dev][PATCH V9 2/2] virtio-spi: add the device specification
Date: Thu, 21 Dec 2023 10:54:31 +0100	[thread overview]
Message-ID: <87a5q3g9t4.fsf@redhat.com> (raw)
In-Reply-To: <86d97639-eb01-4db7-88ec-0adccb45abec@quicinc.com>

On Thu, Dec 21 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:

> Hi Cornelia,
>
> On 12/21/2023 4:44 PM, Cornelia Huck wrote:
>> On Thu, Dec 21 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
>>>> Please move inclusion of this new file into content.tex here, instead of
>>>> including a not-yet-existing file in the previous patch.
>>>>
>>>> (...)
>>>
>>>
>>> Sorry, I don't quite understand here. Maybe I should not add the
>>> following line in content.tex, is that so?
>>>
>>> \input{device-types/spi/description.tex}
>> 
>> No, please add this line; but do so in this patch instead of the
>> previous one that only changes the wording.
>
> I am not clear where to put this line? In the commit message or in the 
> main text, e.g. at the start of the description.tex? As follows:
>
> diff --git a/device-types/spi/description.tex 
> b/device-types/spi/description.tex
> new file mode 100644
> index 0000000..b76258c
> --- /dev/null
> +++ b/device-types/spi/description.tex
> @@ -0,0 +1,281 @@
> +\input{device-types/spi/description.tex}
> +\section{SPI Controller Device}\label{sec:Device Types / SPI Controller 
> Device}
> +
> ...

Ah no, the inclusion is of course in the right place where you put it in
context.tex; the *patch hunk* should be moved from patch 1 to patch 2,
that's all. Hope that's more clear now :)


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: Haixu Cui <quic_haixcui@quicinc.com>,
	virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org,
	harald.mommer@opensynergy.com, broonie@kernel.org,
	qiang4.zhang@linux.intel.com, viresh.kumar@linaro.org
Cc: quic_ztu@quicinc.com
Subject: Re: [virtio-dev][PATCH V9 2/2] virtio-spi: add the device specification
Date: Thu, 21 Dec 2023 10:54:31 +0100	[thread overview]
Message-ID: <87a5q3g9t4.fsf@redhat.com> (raw)
In-Reply-To: <86d97639-eb01-4db7-88ec-0adccb45abec@quicinc.com>

On Thu, Dec 21 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:

> Hi Cornelia,
>
> On 12/21/2023 4:44 PM, Cornelia Huck wrote:
>> On Thu, Dec 21 2023, Haixu Cui <quic_haixcui@quicinc.com> wrote:
>>>> Please move inclusion of this new file into content.tex here, instead of
>>>> including a not-yet-existing file in the previous patch.
>>>>
>>>> (...)
>>>
>>>
>>> Sorry, I don't quite understand here. Maybe I should not add the
>>> following line in content.tex, is that so?
>>>
>>> \input{device-types/spi/description.tex}
>> 
>> No, please add this line; but do so in this patch instead of the
>> previous one that only changes the wording.
>
> I am not clear where to put this line? In the commit message or in the 
> main text, e.g. at the start of the description.tex? As follows:
>
> diff --git a/device-types/spi/description.tex 
> b/device-types/spi/description.tex
> new file mode 100644
> index 0000000..b76258c
> --- /dev/null
> +++ b/device-types/spi/description.tex
> @@ -0,0 +1,281 @@
> +\input{device-types/spi/description.tex}
> +\section{SPI Controller Device}\label{sec:Device Types / SPI Controller 
> Device}
> +
> ...

Ah no, the inclusion is of course in the right place where you put it in
context.tex; the *patch hunk* should be moved from patch 1 to patch 2,
that's all. Hope that's more clear now :)


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-12-21  9:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  3:33 [virtio-comment] [virtio-dev][PATCH V9 0/2] virtio-spi: add virtual SPI controller Haixu Cui
2023-12-12  3:33 ` Haixu Cui
2023-12-12  3:33 ` [virtio-comment] [virtio-dev][PATCH V9 1/2] content: Rename SPI master to " Haixu Cui
2023-12-12  3:33   ` Haixu Cui
2023-12-12  3:33 ` [virtio-comment] [virtio-dev][PATCH V9 2/2] virtio-spi: add the device specification Haixu Cui
2023-12-12  3:33   ` Haixu Cui
2023-12-18 11:04   ` [virtio-comment] " Cornelia Huck
2023-12-18 11:04     ` Cornelia Huck
2023-12-21  3:57     ` [virtio-comment] " Haixu Cui
2023-12-21  3:57       ` Haixu Cui
2023-12-21  8:44       ` [virtio-comment] " Cornelia Huck
2023-12-21  8:44         ` Cornelia Huck
2023-12-21  9:37         ` [virtio-comment] " Haixu Cui
2023-12-21  9:37           ` Haixu Cui
2023-12-21  9:54           ` Cornelia Huck [this message]
2023-12-21  9:54             ` Cornelia Huck
2023-12-26  3:05             ` [virtio-comment] " Haixu Cui
2023-12-26  3:05               ` [virtio-dev] " Haixu Cui
2023-12-21 11:25   ` Harald Mommer
2023-12-21 11:25     ` Harald Mommer
2023-12-22  2:28     ` [virtio-comment] " Haixu Cui
2023-12-22  2:28       ` Haixu Cui
2023-12-22 14:32       ` [virtio-comment] " Harald Mommer
2023-12-22 14:32         ` Harald Mommer
2023-12-26  4:15         ` [virtio-comment] " Haixu Cui
2023-12-26  4:15           ` Haixu Cui
2024-01-02 14:10           ` [virtio-comment] " Harald Mommer
2024-01-02 14:10             ` Harald Mommer
2023-12-22 12:21   ` [virtio-comment] " Cornelia Huck
2023-12-22 12:21     ` Cornelia Huck
2023-12-26  3:11     ` [virtio-comment] " Haixu Cui
2023-12-26  3:11       ` Haixu Cui
2023-12-13  6:54 ` [virtio-comment] Re: [virtio-dev][PATCH V9 0/2] virtio-spi: add virtual SPI controller Haixu Cui
2023-12-13  6:54   ` Haixu Cui

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=87a5q3g9t4.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=broonie@kernel.org \
    --cc=harald.mommer@opensynergy.com \
    --cc=qiang4.zhang@linux.intel.com \
    --cc=quic_haixcui@quicinc.com \
    --cc=quic_ztu@quicinc.com \
    --cc=viresh.kumar@linaro.org \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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.