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>
Subject: Re: [PATCH v8 1/3] m68k: amiga/pcmcia - add 16 bit detection interface to amipcmcia.h
Date: Tue, 9 Nov 2021 10:47:55 +1300 [thread overview]
Message-ID: <c14ea1ed-c3f1-c5f4-c7d6-1b73387bc278@gmail.com> (raw)
In-Reply-To: <CAMuHMdVDAZpG=H210R_qeWmMPFm_62jGgsXv_ymYjDBC5-CcZQ@mail.gmail.com>
Hi Geert,
On 08/11/21 21:35, Geert Uytterhoeven wrote:
> Hi Michael,
>
> On Thu, Nov 4, 2021 at 7:11 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> Add the interface definitions for 16 bit card autoprobing (using
>> the generic PCMCIA cftable entry parser) to amipcmcia.h for use
>> by apne.c.
>>
>> Signed-off-by: Michael Schmitz <schmitzmic@gmail.com>
>
> Thanks for your patch!
>
>> --- a/arch/m68k/include/asm/amipcmcia.h
>> +++ b/arch/m68k/include/asm/amipcmcia.h
>> @@ -64,6 +64,7 @@ static inline void pcmcia_disable_irq(void)
>> #define PCMCIA_SPEED_250NS 250
>> #define PCMCIA_SPEED_720NS 720
>>
>> +#ifndef _LINUX_CISTPL_H
>
> This #ifndef is here to prevent conflicts with <pcmcia/cistpl.h>?
> Why can't the definitions below be removed, and <pcmcia/cistpl.h>
> always included instead?
We'd have to include it everywhere amipcmcia.h is included (because of
the pcmcia_parse_tuple() external declaration below). Didn't want to do
that unless absolutely necessary, but if you don't mind that, I'll
change this part.
>
>> /* PCMCIA Tuple codes */
>>
>> #define CISTPL_NULL 0x00
>> @@ -106,5 +107,8 @@ static inline void pcmcia_disable_irq(void)
>> #define CISTPL_FUNCID_NETWORK 0x06
>> #define CISTPL_FUNCID_AIMS 0x07
>> #define CISTPL_FUNCID_SCSI 0x08
>> +#else /* defined _LINUX_CISTPL_H */
>> +extern int pcmcia_parse_tuple(tuple_t *cftuple, cisparse_t *cfparse);
>
> This can be unconditional?
Brain fade on my part - this of course needs to be conditional on
CONFIG_PCMCIA. not on _LINUX_CISTPL_H.
Cheers,
Michael
>
>> +#endif
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2021-11-08 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 6:10 [PATCH v8 0/3] Add APNE PCMCIA 100 Mbit support Michael Schmitz
2021-11-04 6:10 ` [PATCH v8 1/3] m68k: amiga/pcmcia - add 16 bit detection interface to amipcmcia.h Michael Schmitz
2021-11-08 8:35 ` Geert Uytterhoeven
2021-11-08 21:47 ` Michael Schmitz [this message]
2021-11-09 7:55 ` Geert Uytterhoeven
2021-11-09 19:00 ` Michael Schmitz
2021-11-04 6:10 ` [PATCH v8 2/3] m68k: io_mm.h - add APNE 100 MBit support Michael Schmitz
2021-11-08 8:35 ` Geert Uytterhoeven
2021-11-04 6:10 ` [PATCH v8 3/3] net/8390: apne.c - add 100 Mbit support to apne.c driver Michael Schmitz
2021-11-04 11:19 ` Denis Kirjanov
2021-11-04 21:04 ` Michael Schmitz
2021-11-08 8:38 ` Geert Uytterhoeven
2021-11-08 21:22 ` Michael Schmitz
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=c14ea1ed-c3f1-c5f4-c7d6-1b73387bc278@gmail.com \
--to=schmitzmic@gmail.com \
--cc=alex@kazik.de \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@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