Hi Oliver,
> > > +skip_waking:
> > > usb_anchor_urb(urb, &data->tx_anchor);
> > >
> > > err = usb_submit_urb(urb, GFP_ATOMIC);
> > > @@ -646,10 +723,13 @@ static int btusb_send_frame(struct sk_buff *skb)
> > > BT_ERR("%s urb %p submission failed", hdev->name, urb);
> > > kfree(urb->setup_packet);
> > > usb_unanchor_urb(urb);
> > > + } else {
> > > + usb_mark_last_busy(data->udev);
> > > }
> > >
> > > usb_free_urb(urb);
> > >
> > > +out:
> > > return err;
> > > }
> >
> > Please call the labels simply skip and done.
>
> In this particular case skip_waking seems to be clearer because it
> tells you right away what is skipped.
agree, keep it then.
> > > @@ -721,8 +801,19 @@ static void btusb_work(struct work_struct *work)
> > > {
> > > struct btusb_data *data = container_of(work, struct btusb_data,
> > > work); struct hci_dev *hdev = data->hdev;
> > > + int err;
> > >
> > > if (hdev->conn_hash.sco_num > 0) {
> > > + if (!data->did_iso_resume) {
> > > + err = usb_autopm_get_interface(data->isoc);
> > > + if (!err) {
> > > + data->did_iso_resume = 1;
> > > + } else {
> > > + clear_bit(BTUSB_ISOC_RUNNING,
> > > &data->flags);
> > > + usb_kill_anchored_urbs(&data->isoc_anchor);
> > > + return;
> > > + }
> >
> > Having this as like this is simpler to read:
> >
> > if (err < 0) {
> > clear_bit(BTUSB_ISOC_RUNNING, &data->flags);
> > usb_kill_anchored_urbs(&data->isoc_anchor);
> > return;
> > }
> >
> > data->did_iso_resume = 1;
>
> Do you generally prefer the "else" branch implicit?
I prefer: if error, cleanup and leave function. It is easier to read and
understand by people that are not familiar enough with the code.
If we have a lot of else branches you have to think too much which one
gets executed in case of success. If the command and the follow command
in case of success are on the same indentation, I find it a lot simpler
to follow. My take on these :)
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
