Re: [Bluez PATCH v3 00/12] Inclusive language changes

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

 



Hi Archie,

> This series of patches promotes the usage of the more inclusive terms
> such as central/peripheral, accept list/reject list, or their
> equivalent where appropriate.
> 
> This is also reflected on the changes to Core spec v5.3 and the
> appropriate language mapping table by Bluetooth SIG
> https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf
> 
> As you suggested, I dropped the Android changes and merge patches
> which belong to the same directory into one patch.
> 
> Note that the following terms are not replaced:
> (1) those involving storage format (i.e. storing LTK)
> (2) those which belong to the libbluetooth API
> 
> Thanks,
> Archie
> 
> Changes in v3:
> * Not replacing some terms which belong to libluetooth API
> 
> Changes in v2:
> * Merging several patches from the same directory into one
> 
> Archie Pusaka (12):
>  lib: Inclusive language changes
>  btio: Inclusive language changes
>  monitor: Inclusive language changes
>  emulator: Inclusive language changes
>  tools: Inclusive language changes
>  plugins/sixaxis: Inclusive language changes
>  profiles: Inclusive language changes
>  src: Inclusive language changes
>  client: Inclusive language changes
>  mesh: Inclusive language changes
>  unit/mesh: Inclusive language changes
>  doc: Inclusive language update

so besides the parameter issue for the tools, this looks fine. However I rather apply a whole set of patches instead of cherry-picking. You can even send them into two or three batches so we can apply them quicker.

Regards

Marcel




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux