On 3/4/25 11:32 AM, Paul Barker wrote:
On 03/03/2025 23:16, Marek Vasut wrote:
On 3/3/25 8:29 PM, Paul Barker wrote:
On 02/03/2025 01:24, Marek Vasut wrote:
Move miiphybb operations into separate struct bb_miiphy_bus_ops
structure, add pointer to struct bb_miiphy_bus_ops into the base
struct b
On 02/03/2025 01:24, Marek Vasut wrote:
> Move miiphybb operations into separate struct bb_miiphy_bus_ops
> structure, add pointer to struct bb_miiphy_bus_ops into the base
> struct bb_miiphy_bus and access the ops through this pointer in
> miiphybb generic code. The variable reshuffling in miiphyb
On 03/03/2025 23:16, Marek Vasut wrote:
> On 3/3/25 8:29 PM, Paul Barker wrote:
>> On 02/03/2025 01:24, Marek Vasut wrote:
>>> Move miiphybb operations into separate struct bb_miiphy_bus_ops
>>> structure, add pointer to struct bb_miiphy_bus_ops into the base
>>> struct bb_miiphy_bus and access the
On 3/3/25 8:29 PM, Paul Barker wrote:
On 02/03/2025 01:24, Marek Vasut wrote:
Move miiphybb operations into separate struct bb_miiphy_bus_ops
structure, add pointer to struct bb_miiphy_bus_ops into the base
struct bb_miiphy_bus and access the ops through this pointer in
miiphybb generic code. Th
On 02/03/2025 01:24, Marek Vasut wrote:
> Move miiphybb operations into separate struct bb_miiphy_bus_ops
> structure, add pointer to struct bb_miiphy_bus_ops into the base
> struct bb_miiphy_bus and access the ops through this pointer in
> miiphybb generic code. The variable reshuffling in miiphyb
Move miiphybb operations into separate struct bb_miiphy_bus_ops
structure, add pointer to struct bb_miiphy_bus_ops into the base
struct bb_miiphy_bus and access the ops through this pointer in
miiphybb generic code. The variable reshuffling in miiphybb.c
cannot be easily avoided.
Signed-off-by: Ma
6 matches
Mail list logo
