From: Maarten Brock <m.brock@vanmierlo.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-serial-owner@vger.kernel.org
Subject: Re: [PATCH v2 0/4] serial: uartps: Driver updates
Date: Thu, 20 Dec 2018 12:04:30 +0100 [thread overview]
Message-ID: <923d0af3a92f4be6e064de90db0925ea@vanmierlo.com> (raw)
In-Reply-To: <be121f63-fe03-8b50-54e5-24865d856e56@xilinx.com>
On 2018-12-20 07:52, Michal Simek wrote:
> Hi,
>
> On 19. 12. 18 19:40, Maarten Brock wrote:
>> Hello Michal,
>>
>> On 2018-12-18 13:18, Michal Simek wrote:
>>> Hi,
>>>
>>> I am sending 4 patches in series to fix some issues we found.
>>> Patches were sent separately but I have been asked to send them in
>>> serial that's why I am also adding cover letter to explain this v2
>>> version.
>>>
>>> Thanks,
>>> Michal
>>
>> I'm wondering why, when reading the linux-serial mailing list, I can
>> only see this cover letter.
>> Are you perhaps using a different To/Cc for the actual patches? And if
>> so, is that on purpose?
>>
>
> I have checked linux-serial mailing list and I see all of them there.
> https://www.spinics.net/lists/linux-serial/
>
> Individual here.
> https://www.spinics.net/lists/linux-serial/msg32919.html
> https://www.spinics.net/lists/linux-serial/msg32916.html
> https://www.spinics.net/lists/linux-serial/msg32917.html
> https://www.spinics.net/lists/linux-serial/msg32918.html
>
> Also I see linux-serial@ in CC in all emails I have sent.
>
> Thanks,
> Michal
Thanks, I see them there too. But the odd thing is that I did not
receive
them in my mailbox. And I had noticed this before that I was missing
your
posts following a cover letter.
I normally do receive other peoples patches after a cover letter.
Maarten
WARNING: multiple messages have this Message-ID (diff)
From: Maarten Brock <m.brock@vanmierlo.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: monstr@monstr.eu, linux-serial-owner@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Jiri Slaby <jslaby@suse.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] serial: uartps: Driver updates
Date: Thu, 20 Dec 2018 12:04:30 +0100 [thread overview]
Message-ID: <923d0af3a92f4be6e064de90db0925ea@vanmierlo.com> (raw)
In-Reply-To: <be121f63-fe03-8b50-54e5-24865d856e56@xilinx.com>
On 2018-12-20 07:52, Michal Simek wrote:
> Hi,
>
> On 19. 12. 18 19:40, Maarten Brock wrote:
>> Hello Michal,
>>
>> On 2018-12-18 13:18, Michal Simek wrote:
>>> Hi,
>>>
>>> I am sending 4 patches in series to fix some issues we found.
>>> Patches were sent separately but I have been asked to send them in
>>> serial that's why I am also adding cover letter to explain this v2
>>> version.
>>>
>>> Thanks,
>>> Michal
>>
>> I'm wondering why, when reading the linux-serial mailing list, I can
>> only see this cover letter.
>> Are you perhaps using a different To/Cc for the actual patches? And if
>> so, is that on purpose?
>>
>
> I have checked linux-serial mailing list and I see all of them there.
> https://www.spinics.net/lists/linux-serial/
>
> Individual here.
> https://www.spinics.net/lists/linux-serial/msg32919.html
> https://www.spinics.net/lists/linux-serial/msg32916.html
> https://www.spinics.net/lists/linux-serial/msg32917.html
> https://www.spinics.net/lists/linux-serial/msg32918.html
>
> Also I see linux-serial@ in CC in all emails I have sent.
>
> Thanks,
> Michal
Thanks, I see them there too. But the odd thing is that I did not
receive
them in my mailbox. And I had noticed this before that I was missing
your
posts following a cover letter.
I normally do receive other peoples patches after a cover letter.
Maarten
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-20 11:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 12:18 [PATCH v2 0/4] serial: uartps: Driver updates Michal Simek
2018-12-18 12:18 ` Michal Simek
2018-12-18 12:18 ` [PATCH v2 1/4] serial: uartps: Add the device_init_wakeup Michal Simek
2018-12-18 12:18 ` Michal Simek
2018-12-18 12:18 ` [PATCH v2 2/4] serial: uartps: Check if the device is a console Michal Simek
2018-12-18 12:18 ` Michal Simek
2018-12-18 12:18 ` [PATCH v2 3/4] serial: uartps: Fix error path when alloc failed Michal Simek
2018-12-18 12:18 ` Michal Simek
2018-12-18 12:18 ` [PATCH v2 4/4] serial: uartps: Fix interrupt mask issue to handle the RX interrupts properly Michal Simek
2018-12-18 12:18 ` Michal Simek
2018-12-19 18:40 ` [PATCH v2 0/4] serial: uartps: Driver updates Maarten Brock
2018-12-19 18:40 ` Maarten Brock
2018-12-19 18:40 ` Maarten Brock
2018-12-20 6:52 ` Michal Simek
2018-12-20 6:52 ` Michal Simek
2018-12-20 6:52 ` Michal Simek
2018-12-20 11:04 ` Maarten Brock [this message]
2018-12-20 11:04 ` Maarten Brock
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=923d0af3a92f4be6e064de90db0925ea@vanmierlo.com \
--to=m.brock@vanmierlo.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial-owner@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=shubhrajyoti.datta@xilinx.com \
/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.