On Sat, May 25, 2019 at 09:27:48AM -0500, J Sisson wrote:
> Noticed a typo in jme(4) printf output. Found additional typos while
> browsing the code.
>
> Yes, possibly the most useless diff ever...I freely admit it.
>
fixed, thanks (though note your diff didn;t apply).
jmc
> Index: sys/dev/pci/if_jme.c
> ===================================================================
> RCS file: /cvs/src/sys/dev/pci/if_jme.c,v
> retrieving revision 1.51
> diff -u -p -u -r1.51 if_jme.c
> --- sys/dev/pci/if_jme.c 29 Mar 2019 17:25:44 -0000 1.51
> +++ sys/dev/pci/if_jme.c 25 May 2019 14:19:46 -0000
> @@ -233,7 +233,7 @@ jme_miibus_statchg(struct device *dev)
> * Disabling Rx/Tx MACs have a side-effect of resetting
> * JME_TXNDA/JME_RXNDA register to the first address of
> * Tx/Rx descriptor address. So driver should reset its
> - * internal procucer/consumer pointer and reclaim any
> + * internal producer/consumer pointer and reclaim any
> * allocated resources. Note, just saving the value of
> * JME_TXNDA and JME_RXNDA registers before stopping MAC
> * and restoring JME_TXNDA/JME_RXNDA register is not
> @@ -277,7 +277,7 @@ jme_miibus_statchg(struct device *dev)
>
> /*
> * Reuse configured Rx descriptors and reset
> - * procuder/consumer index.
> + * producer/consumer index.
> */
> sc->jme_cdata.jme_rx_cons = 0;
>
> @@ -550,7 +550,7 @@ jme_attach(struct device *parent, struct
> * JMC250 supports both memory mapped and I/O register space
> * access. Because I/O register access should use different
> * BARs to access registers it's waste of time to use I/O
> - * register spce access. JMC250 uses 16K to map entire memory
> + * register space access. JMC250 uses 16K to map entire memory
> * space.
> */
>
> @@ -984,7 +984,7 @@ jme_dma_free(struct jme_softc *sc)
> /*
> * Unlike other ethernet controllers, JMC250 requires
> * explicit resetting link speed to 10/100Mbps as gigabit
> - * link will cunsume more power than 375mA.
> + * link will consume more power than 375mA.
> * Note, we reset the link speed to 10/100Mbps with
> * auto-negotiation but we don't know whether that operation
> * would succeed or not as we have no control after powering
> @@ -1169,7 +1169,7 @@ jme_encap(struct jme_softc *sc, struct m
> sc->jme_cdata.jme_tx_prod = prod;
> /*
> * Finally request interrupt and give the first descriptor
> - * owenership to hardware.
> + * ownership to hardware.
> */
> desc = txd->tx_desc;
> desc->flags |= htole32(JME_TD_OWN | JME_TD_INTR);
> @@ -1534,7 +1534,7 @@ jme_txeof(struct jme_softc *sc)
> /*
> * Only the first descriptor of multi-descriptor
> * transmission is updated so driver have to skip entire
> - * chained buffers for the transmiited frame. In other
> + * chained buffers for the transmitted frame. In other
> * words, JME_TD_OWN bit is valid only at the first
> * descriptor of a multi-descriptor transmission.
> */
> @@ -2110,7 +2110,7 @@ jme_stop_rx(struct jme_softc *sc)
> break;
> }
> if (i == 0)
> - printf("%s: stopping recevier timeout!\n",
> sc->sc_dev.dv_xname);
> + printf("%s: stopping receiver timeout!\n",
> sc->sc_dev.dv_xname);
> }
>
> void
>
