Re: aufs vs. m68k conflict, please advice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ben Hutchings dixit:

why other architectures get away with it.  Maybe they just don't use
pr_*() in headers.

Maybe something like this?

#define ack_bad_irq(irq) do {					\
	pr_crit("unexpected IRQ trap at vector %02x\n",		\
	    (unsigned int)(irq));				\
} while (/* CONSTCOND */ 0)

This would defer pr_crit expansion to when the static inline
function was actually used.

Just an idea of the moment,
//mirabilos
-- 
  “Having a smoking section in a restaurant is like having
          a peeing section in a swimming pool.”
						-- Edward Burr
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux