> -----Original Message----- > From: Marc Zyngier <maz@xxxxxxxxxx> > Sent: Saturday, August 13, 2022 6:57 AM > To: Frank Li <frank.li@xxxxxxx> > Cc: tglx@xxxxxxxxxxxxx; robh+dt@xxxxxxxxxx; > krzysztof.kozlowski+dt@xxxxxxxxxx; shawnguo@xxxxxxxxxx; > s.hauer@xxxxxxxxxxxxxx; kw@xxxxxxxxx; bhelgaas@xxxxxxxxxx; > devicetree@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux- > pci@xxxxxxxxxxxxxxx; Peng Fan <peng.fan@xxxxxxx>; Aisheng Dong > <aisheng.dong@xxxxxxx>; jdmason@xxxxxxxx; kernel@xxxxxxxxxxxxxx; > festevam@xxxxxxxxx; dl-linux-imx <linux-imx@xxxxxxx>; kishon@xxxxxx; > lorenzo.pieralisi@xxxxxxx; ntb@xxxxxxxxxxxxxxx; lznuaa@xxxxxxxxx > Subject: [EXT] Re: [PATCH v4 2/4] irqchip: imx mu worked as msi controller > > Caution: EXT Email > > On Fri, 12 Aug 2022 22:52:40 +0100, > Frank Li <Frank.Li@xxxxxxx> wrote: > > > > MU support generate irq by write data to a register. > > This patch make mu worked as msi controller. > > So MU can do doorbell by using standard msi api. > > > > Signed-off-by: Frank Li <Frank.Li@xxxxxxx> > > May I add that it wouldn't hurt if you checked what addresses you send > your patches to? For example, 'kernel@xxxxxxxxxxxxxxx' doesn't exist > (maybe you meant linux-kernel@...). [Frank Li] Thanks. Strang, My email system have not report error. > > I will not take patches that haven't been posted to LKML (and I > shouldn't have reviewed it the first place). > > Thanks, > > M. > > -- > Without deviation from the norm, progress is not possible.
