From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
ALeX Kazik <alex@kazik.de>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v5 2/2] net/8390: apne.c - add 100 Mbit support to apne.c driver
Date: Mon, 21 Jun 2021 07:36:26 +1200 [thread overview]
Message-ID: <1bab15e8-df1a-a4bc-fb3c-e0461f64197b@gmail.com> (raw)
In-Reply-To: <CAMuHMdXPY6w3_rg9nKkiZc1d-bEW84G8xzD0kYEqRiwj6hLWhA@mail.gmail.com>
Hi Geert,
On 20/06/21 11:47 pm, Geert Uytterhoeven wrote:
>
>>> Thanks for your patch!
>>>
>>> Note that this patch has a hard dependency on "[PATCH v5 1/2] m68k:
>>> io_mm.h - add APNE 100 MBit support" in the series, so it must not
>>> be applied to the netdev tree yet.
>> Hmm - so we ought to protect the new code by
>>
>> #ifdef ARCH_HAVE_16BIT_PCMCIA
>>
>> and set that in the m68k machine Kconfig in the first patch?
>>
>> (It's almost, but not quite like a config option :-)
> No, we just manage dependencies, so either:
> 1. Patch 2 cannot go in until patch 1 is upstream,
> 2. One subsystem maintainer gives an Acked-by for one patch,so
> the other subsystem maintainer can apply both patches.
I haven't had any review from netdev yet - option 1 looks more feasible
(if you want to carry a patch that's useless without its follow-up). And
with the autoprobe failing (if I understood Alex right), I'll have to
think of something else or drop that patch again.
Is there anything (aside from linking to the e-mail thread) that I can
do to help netdev maintainers locate the first patch? The commit ID
won't remain the same once accepted upstream, am I right?
Cheers,
Michael
>
> Gr{oetje,eeting}s,
>
> Geert
>
prev parent reply other threads:[~2021-06-20 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1624062891-22762-1-git-send-email-schmitzmic@gmail.com>
2021-06-19 0:34 ` [PATCH net-next v5 2/2] net/8390: apne.c - add 100 Mbit support to apne.c driver Michael Schmitz
2021-06-19 0:56 ` Finn Thain
2021-06-19 3:13 ` Michael Schmitz
2021-06-19 9:08 ` Geert Uytterhoeven
2021-06-19 19:31 ` Michael Schmitz
2021-06-20 11:47 ` Geert Uytterhoeven
2021-06-20 19:36 ` Michael Schmitz [this message]
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=1bab15e8-df1a-a4bc-fb3c-e0461f64197b@gmail.com \
--to=schmitzmic@gmail.com \
--cc=alex@kazik.de \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).