From: Jan Beulich <jbeulich@suse.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org,
mingw-w64-public@lists.sourceforge.net
Subject: Re: Problems when building NT kernel drivers with GCC / LD
Date: Mon, 28 Nov 2022 09:07:02 +0100 [thread overview]
Message-ID: <ed50b32a-3bfd-3f3f-1cdf-d2de140697be@suse.com> (raw)
In-Reply-To: <20221126190445.z6kfhqkeesusmuae@pali>
On 26.11.2022 20:04, Pali Rohár wrote:
> On Monday 21 November 2022 08:24:36 Jan Beulich wrote:
>> But then, with you replying to
>> me specifically, perhaps you're wrongly assuming that I would be
>> planning to look into addressing any or all of these? My earlier reply
>> was merely to point out that _some_ work has already been done ...
>
> I added into CC also gcc, ld and mingw mailing list. If this is not
> enough, could you tell me who to contact about those issues?
That's probably enough, sure. I merely tried to set expectations right,
since you did reply To: me (and lists were only on Cc: - it being the
other way around would have demonstrated that you're not asking me
specifically).
Jan
next prev parent reply other threads:[~2022-11-28 8:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 0:06 Pali Rohár
2022-10-30 7:06 ` [Mingw-w64-public] " Martin Storsjö
2022-10-30 19:58 ` ralph engels
2022-10-31 9:55 ` Jan Beulich
2022-11-05 0:57 ` Pali Rohár
2022-11-05 1:26 ` Pali Rohár
2022-11-20 13:10 ` Pali Rohár
2022-11-21 7:24 ` Jan Beulich
2022-11-26 19:04 ` Pali Rohár
2022-11-28 8:07 ` Jan Beulich [this message]
2022-11-28 8:40 ` Jonathan Wakely
2022-11-28 9:06 ` Jan Beulich
2022-12-26 10:47 ` Pali Rohár
2023-01-03 11:06 ` Nick Clifton
2023-02-20 18:25 ` Pali Rohár
2023-04-01 9:23 ` Pali Rohár
2023-04-12 9:53 ` Nick Clifton
2023-04-12 20:40 ` Pali Rohár
2024-01-07 1:55 ` Pali Rohár
2024-04-07 23:20 ` Pali Rohár
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=ed50b32a-3bfd-3f3f-1cdf-d2de140697be@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=mingw-w64-public@lists.sourceforge.net \
--cc=pali.rohar@gmail.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).